Techniques for hot snapshots for message syncing

ABSTRACT

Techniques for hot snapshotting for message syncing are described. An apparatus may comprise a network component and a snapshot component. The network component may be operative to receiving an incoming update. The snapshot component may be operative to retrieve a messaging snapshot for a user associated with the incoming update; identify a messaging thread corresponding to the incoming update; apply the incoming update to the messaging thread; determining that a number of messaging threads stored in the messaging snapshot is greater than a thread storage limit for the messaging snapshot; identify a least-recently-updated messaging thread currently stored in the messaging snapshot; and remove the least-recently updated messaging thread from the messaging snapshot.

RELATED APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. §119(e)to U.S. Provisional Patent Application No. 62/035,663, titled“Techniques for a Persistent Queue for Message Syncing,” filed on Aug.11, 2014, which is hereby incorporated by reference in its entirety.This application claims the benefit of priority under 35 U.S.C. §119(e)to U.S. Provisional Patent Application No. 62/035,665, titled“Techniques for a Sequential Message Reader for Message Syncing,” filedon Aug. 11, 2014, which is hereby incorporated by reference in itsentirety. This application claims the benefit of priority under 35U.S.C. §119(e) to U.S. Provisional Patent Application No. 62/035,668,titled “Techniques for Hot Snapshots for Message Syncing,” filed on Aug.11, 2014, which is hereby incorporated by reference in its entirety.This application claims the benefit of priority under 35 U.S.C. §119(e)to U.S. Provisional Patent Application No. 62/035,673, titled“Techniques for Intelligent Messaging for Message Syncing,” filed onAug. 11, 2014, which is hereby incorporated by reference in itsentirety.

This application is related to a United States patent application with ashared specification and drawings with attorney docket number1360F0055.1, titled “Techniques for a Persistent Queue for MessageSyncing,” filed on Feb. 13, 2015, which is hereby incorporated byreference in its entirety. This application is related to a UnitedStates patent application with a shared specification and drawings withattorney docket number 1360F0055.2, titled “Techniques for a SequentialMessage Reader for Message Syncing,” filed on Feb. 13, 2015, which ishereby incorporated by reference in its entirety. This application isrelated to a United States patent application with a sharedspecification and drawings with attorney docket number 1360F0055.4,titled “Techniques for Intelligent Messaging for Message Syncing,” filedon Feb. 13, 2015, which is hereby incorporated by reference in itsentirety.

BACKGROUND

Internet users may engage in communication with each other, such asthrough the exchange of messages. Users may compose messages to eachother on computing devices and transmit them to each other, such as viaan intermediary messaging platform. Users may have accounts registeredwith the intermediary messaging platform establishing an address atwhich they may be contacted. The users may compose and submit theirmessages using these addresses. Users may receive their correspondenceat their address by accessing the intermediary messaging platform withtheir address and a password associated with their account.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some novel embodiments described herein. This summaryis not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

Various embodiments are generally directed to techniques for apersistent queue for message syncing. Some embodiments are particularlydirected to techniques for a persistent queue for message syncing inwhich a strict sequencing of updates is maintained to advance messagingendpoint sync efficiency.

In one embodiment, for example, an apparatus may comprise a recipientinbound messaging component, a recipient queue management component, anda recipient outbound messaging component. The recipient inboundmessaging component may be operative to receive an incoming update at arecipient update queue, the recipient update queue associated with arecipient of the incoming update. The recipient queue managementcomponent may be operative to determine an incoming recipient sequencenumber for the recipient update queue, the incoming recipient sequencenumber determined by incrementing a highest current recipient sequencenumber for the recipient update queue, assign the incoming recipientsequence number to the incoming update, add the incoming update to therecipient update queue, determine a current recipient sequence numberfor a current recipient update state of a recipient messaging endpointassociated with the recipient of the incoming update, determine that theincoming recipient sequence number is greater than the current recipientsequence number for the current recipient update state of the recipientmessaging endpoint, and update the current recipient sequence number forthe current recipient update state of the recipient messaging endpointto be at least the incoming recipient sequence number. The recipientoutbound messaging component may be operative to transmit the incomingupdate to the recipient messaging endpoint based on the determinationthat the incoming recipient sequence number is greater than the currentrecipient sequence number.

Various embodiments are generally directed to techniques for asequential message reader for message syncing. Some embodiments areparticularly directed to techniques for a sequential message reader formessage syncing in which a strict sequencing of updates is maintained toadvance messaging endpoint sync efficiency.

In another embodiment, an apparatus may comprise a network component andan inbox management component. The network component may be operative toreceiving an incoming update at a messaging endpoint from a recipientupdate queue, the incoming update comprising an incoming recipientsequence number. The inbox management component may be operative to addthe incoming update to a message inbox on the messaging endpoint, theincoming update added to the message inbox in an order determined by theincoming recipient sequence number and determine based on the incomingrecipient sequence number whether one or more additional updates aremissing from the message inbox on the messaging endpoint.

Various embodiments are generally directed to techniques for hotsnapshots for message syncing. Some embodiments are particularlydirected to techniques for hot snapshots for message syncing in which astrict sequencing of updates is maintained to advance messaging endpointsync efficiency.

In another embodiment, an apparatus may comprise a network component anda snapshot component. The network component may be operative toreceiving an incoming update. The snapshot component may be operative toretrieve a messaging snapshot for a user associated with the incomingupdate; identify a messaging thread corresponding to the incomingupdate; apply the incoming update to the messaging thread; determiningthat a number of messaging threads stored in the messaging snapshot isgreater than a thread storage limit for the messaging snapshot; identifya least-recently-updated messaging thread currently stored in themessaging snapshot; and remove the least-recently updated messagingthread from the messaging snapshot.

Various embodiments are generally directed to techniques for intelligentmessaging for message syncing. Some embodiments are particularlydirected to techniques for intelligent messaging for message syncing inwhich a strict sequencing of updates is maintained to advance messagingendpoint sync efficiency.

In another embodiment, an apparatus may comprise a recipient inboundmessaging component, a recipient queue management component, a recipientupdate customization component, and a recipient outbound messagingcomponent. The recipient inbound messaging component may be operative toreceive an incoming update at a recipient update queue, the recipientupdate queue associated with a recipient of the incoming update. Therecipient queue management component may be operative to add theincoming update to the recipient update queue and determine a recipientmessaging endpoint to receive the incoming update. The recipient updatecustomization component may be operative to retrieve one or morerecipient messaging endpoint parameters associated with the recipientmessaging endpoint and generate a customized incoming update from theincoming update according to the one or more recipient messagingendpoint parameters. The recipient outbound messaging component may beoperative to transmit the customized incoming update to the recipientmessaging endpoint.

Other embodiments are described and claimed.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of the various ways in which the principles disclosed hereincan be practiced and all aspects and equivalents thereof are intended tobe within the scope of the claimed subject matter. Other advantages andnovel features will become apparent from the following detaileddescription when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a messaging system.

FIG. 2 illustrates an embodiment of an incoming messaging being added toa sender update queue.

FIG. 3 illustrates an embodiment of an incoming update being forwardedfrom a sender update queue to a recipient update queue.

FIG. 4 illustrates an embodiment of an incoming messaging being sentfrom a recipient update queue to a recipient messaging endpoint.

FIG. 5 illustrates an embodiment of a messaging server managing arecipient update queue.

FIG. 6 illustrates an embodiment of a messaging server managing a senderupdate queue.

FIG. 7 illustrates an embodiment of messaging endpoints sending andreceiving a message.

FIG. 8 illustrates an embodiment of a snapshot component.

FIG. 9 illustrates an embodiment of a messaging server customizing anupdate for a messaging endpoint.

FIG. 10A illustrates an embodiment of a first logic flow for the systemof FIG. 1.

FIG. 10B illustrates an embodiment of a second logic flow for the systemof FIG. 1.

FIG. 10C illustrates an embodiment of a third logic flow for the systemof FIG. 1.

FIG. 10D illustrates an embodiment of a fourth logic flow for the systemof FIG. 1.

FIG. 11 illustrates an embodiment of a centralized system for the systemof FIG. 1.

FIG. 12 illustrates an embodiment of a distributed system for the systemof FIG. 1.

FIG. 13 illustrates an embodiment of a computing architecture.

FIG. 14 illustrates an embodiment of a communications architecture.

FIG. 15 illustrates an embodiment of a radio device architecture.

DETAILED DESCRIPTION

Various embodiments are directed to techniques for updating multiplemessaging endpoints using a persistent update queue that maintains statefor each of the multiple messaging endpoints. These techniques areparticularly directed to cases in which the messaging endpoints arebandwidth-limited, such as for mobile devices that commonly operate on acellular network.

A message service may operate by defining a messaging inbox ascomprising a plurality of messages, wherein each message is anindividual transaction of communication between two or moreparticipants. A mail server may operate by maintaining a message indexfor the messaging inbox. Mail servers may receive messages and store themessages in mail archives from which messages may be retrieved throughreference to the message index. Mail clients may connect to the mailservers and retrieve messages that have been added to their mail archivesince their last update. The mail clients may receive a mail index fromthe mail archive indicating what messages are stored in the mailarchive. The mail clients may compare the mail archive to their currentinbox in order to determine what messages they are missing, which theythen request from the mail archive. The mail clients may make changes totheir inbox, which results in mail inbox instructions being transmittedto the mail archives instructing the mail archives in modifications tomake to the representation of their mail inbox on the mail archives.

Unfortunately, the transmission of a messaging inbox index may involve alarge transfer of data inappropriate for mobile devices. Instead, amessaging endpoint may benefit from a messaging platform transmitting itatomic updates to the message inbox that iteratively update the messageinbox on the messaging endpoint from its existing state to the currentstate reflected at the messaging platform. Further, the messagingendpoint may benefit from the messaging platform maintaining the currentupdate state of the message inbox on the messaging endpoint. When themessaging endpoint connects to the messaging platform, or otherwisebecomes network-accessible, the messaging platform may determine whetherthe messaging endpoint has any updates pending without the messagingendpoint having to update the messaging platform as to its currentstatus.

Further, a messaging endpoint with intermittent connectivity may, duringa period of connectivity, receive a subset of the available updates andbe left in a consistent state. A messaging endpoint may gainconnectivity, receive the subset of available updates, loseconnectivity, and during the period of disconnection the user may readany new messages that were received. Once connectivity is reestablishedthe update process may resume, the messaging endpoint receiving some orall of the remaining updates from the messaging platform.

As a result, the embodiments may reduce the bandwidth used and radioactivity used by a mobile device to maintain a message inbox. As such,users may receive an improved messaging experience and the messagingplatform may experience improved user satisfaction.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form in order to facilitate adescription thereof. The intention is to cover all modifications,equivalents, and alternatives consistent with the claimed subjectmatter.

It is worthy to note that “a” and “b” and “c” and similar designators asused herein are intended to be variables representing any positiveinteger. Thus, for example, if an implementation sets a value for a=5,then a complete set of components 122 may include components 122-1,122-2, 122-3, 122-4 and 122-5. The embodiments are not limited in thiscontext.

Persistent Queue

FIG. 1 illustrates a messaging system 100 in the context of an operatingenvironment for a user. As shown in FIG. 1, a user may make use of aplurality of computing devices with a messaging server 110.

The messaging server 110 may be one of a plurality of messaging serversoperating by a messaging platform as part of the messaging system 100.The messaging server 110 may comprise an Internet-accessible server,with the network 120 connecting the various devices of the messagingsystem 100 comprising, at least in part, the Internet.

A user may own and operate a smartphone device 150. The smartphonedevice 150 may comprise an iPhone® device, an Android® device, aBlackberry® device, or any other mobile computing device conforming to asmartphone form. The smartphone device 150 may be a cellular devicecapable of connecting to a network 120 via a cell system 130 usingcellular signals 135. In some embodiments and in some cases thesmartphone device 150 may additionally or alternatively use Wi-Fi orother networking technologies to connect to the network 120. Thesmartphone device 150 may execute a messaging client, web browser, orother local application to access the messaging server 110.

The same user may own and operate a tablet device 160. The tablet device150 may comprise an iPad® device, an Android® tablet device, a KindleFire® device, or any other mobile computing device conforming to atablet form. The tablet device 160 may be a Wi-Fi device capable ofconnecting to a network 120 via a Wi-Fi access point 140 using Wi-Fisignals 145. In some embodiments and in some cases the tablet device 160may additionally or alternatively use cellular or other networkingtechnologies to connect to the network 120. The tablet device 160 mayexecute a messaging client, web browser, or other local application toaccess the messaging server 110.

The same user may own and operate a personal computer device 180. Thepersonal computer device 180 may comprise a Mac OS® device, Windows®device, Linux® device, or other computer device running anotheroperating system. The personal computer device 180 may be an Ethernetdevice capable of connecting to a network 120 via an Ethernetconnection. In some embodiments and in some cases the personal computerdevice 180 may additionally or alternatively use cellular, Wi-Fi, orother networking technologies to the network 120. The personal computerdevice 180 may execute a messaging client, web browser 170, or otherlocal application to access the messaging server 110.

A messaging client may be a dedicated messaging client. A dedicatedmessaging client may be specifically associated with a messagingprovider administering the messaging platform including the messagingserver 110. A dedicated messaging client may be a general clientoperative to work with a plurality of different messaging providersincluding the messaging provider administering the messaging platformincluding the messaging server 110.

The messaging client may be a component of an application providingadditional functionality. For example, a social networking service mayprovide a social networking application for use on a mobile device foraccessing and using the social networking service. The social networkingservice may include messaging functionality such as may be provided bymessaging server 110. It will be appreciated that the messaging server110 may be one component of a computing device for the social networkingservice, with the computing device providing additional functionality ofthe social networking service. Similarly, the social networkingapplication may provide both messaging functionality and additionalsocial networking functionality.

In some cases a messaging endpoint may retain state between usersessions and in some cases a messaging endpoint may relinquish statebetween user session. A messaging endpoint may use a local store toretain the current state of a message inbox. This local store may besaved in persistent storage such that the state may be retrieved betweenone session and the next, including situations in which, for example, alocal application is quit or otherwise removed from memory or a deviceis powered off and on again. Alternatively, a messaging endpoint may usea memory cache to retain the current state of a message inbox butrefrain from committing the state of the message inbox to persistentstorage.

A messaging endpoint that retains the state of a message inbox maycomprise a dedicated messaging application or a messaging utilityintegrated into another local application, such as a social networkingapplication. A messaging endpoint that relinquishes state of a messageinbox may comprise messaging access implemented within a web browser. Inone embodiment, a web browser, such as web browser 170 executing onpersonal computer device 180, may execute HTML5 code that interacts withthe messaging server to present messaging functionality to a user.

A user may send and receive messages from a plurality of devices,including the smartphone device 150, tablet device 160, and personalcomputer device 180. The user may use a first messaging application onthe smartphone device 150, a second messaging application on the tabletdevice 160, and the web browser 170 on the personal computer device 180.The first and second messaging applications may comprise installationsof the same application on both devices. The first and second messagingapplications may comprise a smartphone-specific and a tablet-specificversion of a common application. The first and second messagingapplication may comprise distinct applications.

The user may benefit from having their message inbox kept consistentbetween their devices. A user may use their smartphone device 150 on thecell system 130 while away from their home, sending and receivingmessages via the cells system 130. The user may stop by a coffee shop,or other location offering Wi-Fi, and connect their tablet device 160 toa Wi-Fi access point 140. The tablet device 160 may retrieve itsexisting known state for the message inbox and receive updates that havehappened since the last occasion on which the tablet device 160 hadaccess to a network, including any messages sent by the smartphonedevice 150 and that may have been received by the user while operatingthe smartphone device 150. The user may then return home and accesstheir message inbox using a web browser 170 on a personal computerdevice 180. The web browser 170 may receive a snapshot of the currentstate of the message inbox from the messaging server 110 due to it notmaintaining or otherwise not having access to an existing state for themessage inbox. The web browser 170 may then retrieve incremental updatesfor any new changes to the state of the message inbox so long as itmaintains a user session with the messaging server 110, discarding itsknown state for the message inbox at the end of the session, such aswhen the web browser 170 is closed by the user.

FIG. 2 illustrates an embodiment of an incoming update 220 being addedto a sender update queue 230.

A sender messaging endpoint 210 may represent any one of a plurality ofmessaging endpoints used by a user in conjunction with a messagingplatform. The incoming update 220 may represent any one of a pluralityof types of updates supported by the messaging system 100. The incomingupdate 220 may generally correspond to an atomic modification to amessage inbox. The incoming update 220 may comprise a new messageaddressed to one or more users of the messaging system 100. The incomingupdate 220 may comprise a deletion from a message inbox of a message.The incoming update 220 may comprise a notification that a messagereceived by the sender of the incoming update 220 has been read. Theincoming update 220 may comprise any modification to the state of themessage inbox, and in particular a single modification operative to beperformed via an atomic interaction with a message store.

The incoming update 220 may be received at a sender update queue 230.The sender update queue 230 may be specifically associated with the userof sender messaging endpoint 210, such as by being uniquely associatedwithin the messaging system 100 with a user account for the user ofsender messaging endpoint 210. The sender update queue 230 may be asingle queue used for all messaging endpoints used by this user.

The sender update queue 230 may comprise a representation of updates ina strict linear order with a monotonically and incrementally increasingassignment of sequence numbers to represent the strict linear order ofupdates. The sender update queue 230 may be organized as a data unitaccording to a variety of techniques. The sender update queue 230 may bestored in semi-persistent memory, persistent storage, bothsemi-persistent memory and persistent storage, or a combination of thetwo. The sender update queue 230 may be organized according to a varietyof data structures, including linked lists, arrays, and other techniquesfor organizing queues. The sender update queue 230 may generallycomprise a first-in-first-out (FIFO) queue in which no update will beremoved from the queue before any updates that were received prior toit. This may be enforced through a strict requirement that the updatesstored in the queue include a complete set of the integer sequencenumbers from the oldest update in the sender update queue 230 to thenewest update in the sender update queue 230.

Upon reception, an incoming sender sequence number may be determined forthe sender update queue 230, the incoming sender sequence numberdetermined by incrementing a highest current sender sequence number forthe sender update queue 230. The sender update queue 230, as depicted inFIG. 2, already contains updates 240, comprising updates 240-1, 240-2,240-3, 240-4, and 240-5. These fives updates have already been assignedsequence numbers, respectively “1212,” “1213,” “1214,” “1215,” and“1216.” As such, the incoming update 220 may be assigned the sequencenumber “1217,” which is one greater than the highest current sendersequence number “1216.”

The incoming update 220, with the incoming sender sequence number “1217”assigned to it, may then be added to the sender update queue 230. In theillustrated embodiment of FIG. 2, update 240-1, with sequence number“1212,” was removed from the sender update queue 230 in response toincoming update 220 being added. Update 240-1 was the oldest updatestill in the sender update queue 230 and was therefore the first updateto be removed given that any update was removed. This may representthat, in some embodiments, sender update queue 230 may have a fixed ormaximum size. Where sender update queue 230 is a fixed-size queue, anoldest update may be removed from the sender update queue 230 in FIFOorder whenever a new update is added, possibly excluding an initialperiod after the creation of sender update queue 230 during which thefixed size is reached. Where sender update queue 230 is a queue with amaximum, an oldest update may be removed from the sender update queue230 in FIFO order whenever a new update is added if the sender updatequeue 230 is already at its maximum size, but there may also be othercircumstances in which updates are removed from the queue even where anew update would not take the sender update queue 230 above its definedmaximum size. A fixed or maximum size of an update queue may be adefined parameter for a messaging server 110 or messaging system 100.

FIG. 3 illustrates an embodiment of an incoming update 220 beingforwarded from a sender update queue 230 to a recipient update queue330.

The incoming update 220 may be received at a recipient update queue 330from the sender update queue 230. The recipient update queue 330 may beassociated with one recipient of one or more recipients of the incomingupdate 220. A recipient may be determined for an incoming update 220according to a variety of criteria. Where the incoming update 220corresponds to a new message being sent to other users, the recipientsof the update 220 may comprise a recipient list created as part of thecomposition of the new message by the sender. Where the incoming update220 corresponds to an updated status of the sender on a socialnetworking service, the recipient list may be determined by the socialnetworking service based on relationships (e.g., friends, follows,likes) of which the sender is part. Where the incoming update 220corresponds to a posted item shared on a network, the recipient list maybe determined by the network based on users tagged in the shared item(e.g., users tagged as present in a photo). Where the incoming update220 corresponds to a modification to a user's inbox, such as thedeletion of a message, flagging a priority for a message, flagging amessage as read, or other interaction only or primarily relevant to theuser with which the message inbox is associated, the recipient list maybe empty, such that no other users—and therefore no other messagequeues—receive the incoming update 220.

As with the sender update queue 230, the recipient update queue 330 maycomprise a representation of updates in a strict linear order with amonotonically and incrementally increasing assignment of sequencenumbers to represent the strict linear order of updates. The recipientupdate queue 330 may generally comprise a first-in-first-out (FIFO)queue in which no update will be removed from the queue before anyupdates that were received prior to it. This may be enforced through astrict requirement that the updates stored in the queue include acomplete set of the integer sequence numbers from the oldest update inthe recipient update queue 330 to the newest update in the recipientupdate queue 330. The recipient update queue 330 may be organized as adata unit according to a variety of techniques.

Upon reception, an incoming recipient sequence number may be determinedfor the recipient update queue 330, the incoming recipient sequencenumber determined by incrementing a highest current recipient sequencenumber for the recipient update queue 330. The recipient update queue330, as depicted in FIG. 3, already contains updates 340, comprisingupdates 340-1, 340-2, 340-3, 340-4, and 340-5. These fives updates havealready been assigned sequence numbers, respectively “817,” “818,”“819,” “820,” and “821.” As such, the incoming update 220 may beassigned the sequence number “822,” which is one greater than thehighest current sender sequence number “822.”

The incoming update 220 may, therefore, have a different sequence numberat each of the sender update queue 230 and the recipient update queue330. Due to the requirement that the sequence numbers for a given queuebe strictly in sequence and define a strict ordering, the sequencenumbers for the incoming update 220 in each update queue are differentto reflect the position of the incoming update 220 in each update queue.

The incoming update 220, with the incoming sender sequence number “822”assigned to it, may then be added to the recipient update queue 330. Inthe illustrated embodiment of FIG. 3, update 340-1, with sequence number“817,” was removed from the recipient update queue 330 in response toincoming update 220 being added. As with sender update queue 230, therecipient update queue 330 may be a fixed-size queue or queue with adefined maximum size. It will be appreciated that a defined fixed sizeor maximum size may be globally defined for all update queues or may beindividually defined for different update queues. For instance, userswith a higher throughput of updates, such as may correspond to morefrequent use of the messaging system 100, may be allowed larger updatequeues. Users may be able to purchase larger maximum or fixed updatequeue sizes as a premium feature. The maximum or fixed size of an updatequeue may be automatically adjusted for a user to minimize theoccurrence of a messaging endpoint for the user connecting to thatuser's update queue and finding that updates which it has not yetreceived have been removed from the update queue due to the maximum orfixed size restriction.

FIG. 4 illustrates an embodiment of an incoming messaging 220 being sentfrom a recipient update queue 330 to a recipient messaging endpoint 410.

A sender messaging endpoint 410 may represent any one of a plurality ofmessaging endpoints used by a user in conjunction with a messagingplatform. The recipient update queue 330 may be specifically associatedwith the user of recipient messaging endpoint 410, such as by beinguniquely associated within the messaging system 100 with a user accountfor the user of recipient messaging endpoint 410. The recipient updatequeue 330 may be a single queue used for all messaging endpoints used bythis user.

It will be appreciated that the scenario in which an incoming update 220is transmitted from a sender messaging endpoint 210 to a sender updatequeue 230 to a recipient update queue 330 to a recipient messagingendpoint 410 may represent only one possible flow of a plurality offlows of an update through the messaging system 100. It may specificallycorrespond to a flow in which the incoming update 220 is a new messagebeing sent from a sender at the sender messaging endpoint 210 to areceiver at the receiver messaging endpoint 410. In other situations amessaging endpoint such as the recipient messaging endpoint 410 or thesender messaging endpoint 210 may interact with their respective queueswithout an update being forwarded to another queue.

For example, the sender may remove a message from their associatedmessage inbox at the sender messaging endpoint 210, which may cause thesender messaging endpoint 210 to submit an incoming update 220 to thesender message queue 230 indicating this change. The sender messagingendpoint 210 may then receive the incoming update 220 back from thesender message queue 230 with its assigned sequence number indicatingthat the change has been applied and informing the sender messagingendpoint 210 of the sequence number to aid the sender messaging endpoint210 in maintaining synchronization with the sender message queue 230.The incoming update 220 may also be distributed to other messagingendpoint for the sender.

A current recipient sequence number 450 may be determined for a currentupdate state of the recipient messaging endpoint 410 associated with therecipient of the incoming update 220. Where the incoming update 220 isreceived from a distinct sender, the recipient of the incoming update220 may comprise an addressed recipient of a message in addition to thesender of the message receiving their own incoming update 220 toacknowledge its receipt by the messaging system 100. Where the incomingupdate 220 is restricted in relevance to a single user's messaginginbox, the recipient of the incoming update 220 may be the same userinitiating the production of the incoming update 220.

The current recipient sequence number 450 may be retrieved byidentifying the recipient messaging endpoint 410 and retrieving thecurrent recipient sequence number 450 from a data store used for themaintenance of the recipient update queue 330. In some cases, such aswhere a plurality of recipient messaging endpoints are used by therecipient user, a plurality of current recipient sequence numbers may bestored in association with the recipient update queue 330. Each of theplurality of current recipient sequence numbers may correspond to acurrent recipient update state of one of the plurality of recipientmessaging endpoints. For instance, a second current recipient sequencenumber 455 may be associated with the recipient update queue 330 and adifferent recipient messaging endpoint than the recipient messagingendpoint 410. For example, the recipient messaging endpoint 410 maycorrespond to the smartphone device 150 of FIG. 1 while a secondrecipient messaging endpoint may correspond to the tablet device 160.

Determining the current recipient sequence number 450 for the currentrecipient update state of the recipient messaging endpoint 410 maycomprise retrieving the current recipient sequence number 450 based onan identifier for the recipient messaging endpoint 410. Each of theplurality of recipient messaging endpoints for the recipient user may beassociated with an identifier. The recipient update queue 330 may bestored in association with a plurality of identifiers each correspondingto a particular recipient messaging endpoints, with each of theplurality of identifiers associated with a current recipient sequencenumber reflecting the current update state of the associated recipientmessaging endpoint. The current recipient sequence numbers may beexplicitly stored as being the sequence number for the recipient updatequeue 330 that corresponds to the last or most-recent update of theplurality of updates 340 that each recipient messaging endpoint hasreceived. For instance, the recipient messaging endpoint 410 may beup-to-date with the recipient update queue 330 as far as the update340-5 immediately prior to the just-added incoming update 220. As such,the current recipient sequence number 450 for the recipient messagingendpoint 410 may be “821,” the sequence number assigned to the update340-5 at the recipient update queue 330.

Alternatively or additionally, an identifier for a recipient messagingendpoint may include a link or other logical connection to theparticular update that is the most-recent, in regards to the ordering ofthe recipient update queue 330, that the recipient messaging endpointhas received. This may empower, for example, the messaging server 110 toretrieve the link or other logical connection based on the identifierfor the recipient messaging endpoint 410 and follow the link to aposition within the recipient update queue 330 that allows for immediatetraversal through the recipient update queue 330 of those updates thatthe recipient messaging endpoint 410 has not yet received. Similarly, adata structure for the recipient update queue 330 may contain an entry,link, or other signifiers to indicate one or more recipient messagingendpoints for which it is the most-recent update transmitted to thatrecipient messaging endpoint. Any combination of these techniques may beused.

It will be appreciated that the most-recent update transmitted to arecipient messaging endpoint may comprise the update that is most-recentaccording to the ordering provided by the recipient update queue 330. Insome cases, a recipient messaging endpoint 410 may receive updatesout-of-order due to, for example, network transmission problems. Whilethe messaging server 110 may endeavor to transmit the atomic updatesrepresented by the updates 340 to recipient messaging endpoints such asrecipient messaging endpoint 410 in the order that they should beapplied, where a sequence of updates is transmitted an update in themiddle of the sequence may be lost while a later sequence us received.The missed update may be retransmitted from the messaging server 110 tothe recipient messaging endpoint 410 upon recognition that the updatewas missed, and therefore be the most-recent update transmitted in termsof transmission order, but not be the most-recent update in terms of theordering provided by the recipient update queue 330. The currentrecipient sequence number 450 for the recipient messaging endpoint 410may therefore correspond to the sequence number for the update latest inthe ordering of the recipient update queue 330 received by the recipientmessaging endpoint 410 or known to have been received by the recipientmessaging endpoint 410 by the messaging server 110.

It may be determined that the incoming recipient sequence number for theincoming update 220 is greater than the current recipient sequencenumber 450 for the current recipient update state of the recipientmessaging endpoint 410. This may indicate that the incoming update 220has not yet been received by the recipient messaging endpoint 410. Wherethe incoming update 220 has just been added to the recipient updatequeue 330, this may be due to their not having yet been an opportunityto transmit the incoming update 220 to the recipient messaging endpoint410. However, in some cases, the incoming update 220 may have been inthe recipient update queue 330, available for transmission, but not yettransmitted to the recipient messaging endpoint 410 due tounavailability of the recipient messaging endpoint 410.

As such, the incoming update 220 may be transmitted to the recipientmessaging endpoint 410 in response to the recipient messaging endpoint410 becoming available. The recipient messaging endpoint 410 maytransmit an update request to the messaging server 110 in order toreceive any updates it has not yet received, such as incoming update220. The update request 110 may be an explicit request for updates ormay be an implicit request based upon the availability of a networkconnection the recipient messaging endpoint 410. The update request mayinclude the identifier for the recipient messaging endpoint 410 toempower the retrieval of the current recipient sequence number 450.Where the update request is implicit, the identifier may be transmittedas part of a security procedure for the establishment of the connection,such as being included in the transmission of a security token from therecipient messaging endpoint 410 to the messaging system 100. The updaterequest may include the current recipient update state of the recipientmessaging endpoint 410.

The incoming update 220 may be transmitted to the recipient messagingendpoint 410 based on the determination that the incoming recipientsequence number for the incoming update 220 is greater than the currentrecipient sequence number 450. As the recipient messaging endpoint 410is available and has not yet received the incoming update 220, theincoming update 220 is provided to the recipient messaging endpoint 410.

The current recipient sequence number 450 for the current recipientupdate state of the recipient messaging endpoint 410 may then be updatedto be at least the incoming recipient sequence number. As shown in FIG.4, the current recipient sequence number 450 has been changed toindicate that the incoming update 220 has been received by the recipientmessaging endpoint 410 associated with the current recipient sequencenumber 450. Where the incoming update 220 is the most-recent update inthe recipient update queue 330, the current recipient sequence number450 may be set to be precisely the incoming recipient sequence numberassociated with the incoming update 220. However, where newer updatesare also available, those updates may also be transmitted to therecipient messaging endpoint 410, with the current recipient sequencenumber 450 set to be the sequence number for the most-recent of thoseupdates, and therefore a greater value than the incoming recipientsequence number.

In some embodiments, the removal of updates from an update queue such asthe recipient update queue 330 may be performed when all messagingendpoints associated with the update queue have received those updates,such as may be indicated by the current sequence numbers for themessaging endpoints. For example, the user associated with the recipientmessaging endpoint 410 may have two messaging endpoints associated withtheir user account, which may have current sequence numbers representedby the current recipient sequence number 450 and second currentrecipient sequence number 455. Second current recipient sequence number455 indicates that a second recipient messaging endpoint is lessup-to-date than the first recipient messaging endpoint 410, particularlyafter current recipient sequence number 450 is updated to indicate thetransmission of the incoming update 220 to the first recipient messagingendpoint 410. However, as according to the current recipient sequencenumbers, both recipient messaging endpoints for the recipient user havealready received updates 340-2 and 340-3. Given this indication, updates340-2 and 340-3 may be removed from the recipient update queue 330 dueto those updates not longer being needed by any current messagingendpoint that is associated with the recipient update 330.

In general, a plurality of current recipient sequence numbers may bestored in association with the recipient update queue 330, each of theplurality of current recipient sequence numbers associated with adifferent recipient messaging endpoint. It may be determined that everycurrent recipient sequence number of the plurality of current recipientsequence numbers is greater than a sequence number for an old updatestored in the recipient update queue 330. In response to thisdetermination, the old update may be removed from the recipient updatequeue 330.

In some cases, a current sequence number may be used for a messagingendpoint, such as a web browser 170, that does not maintain statebetween sessions. Because the messaging endpoint does not maintain statebetween sessions, it may not be advantageous to maintain a currentsequence number for the messaging endpoint between the sessions of themessaging endpoint with the messaging server 110. Therefore, when amessaging endpoint that discards state between sessions connects to themessaging server 110 the messaging endpoint may be brought up-to-date,which may comprise receiving a current state of a messaging inbox froman archival mail server or inbox snapshot component. A current sequencenumber for the messaging endpoint may be established at the beginning ofthe messaging endpoint's session, such as in response to the messagingendpoint being brought up-to-date by an archival mail server or inboxsnapshot component. The current sequence number for the messagingendpoint may be maintained during the session for the messaging endpointand then discarded when the session ends.

FIG. 5 illustrates a block diagram for a messaging system 100. In oneembodiment, the messaging system 100 may comprise a computer-implementedsystem including one or more software applications comprising one ormore components. Although the messaging system 100 shown in FIG. 5 has alimited number of elements in a certain topology, it may be appreciatedthat the messaging system 100 may include more or less elements inalternate topologies as desired for a given implementation.

The messaging system 100 may comprise a messaging server 110. Themessaging system 100 may comprise an additional messaging server 510.The messaging system 100 may comprise a plurality of messaging serversincluding the messaging server 110 and the messaging server 510.

The messaging server 110 may comprise an inbound messaging component540. The inbound messaging component 540 may be generally arranged toreceive an incoming update 220 at a recipient update queue 330, therecipient update queue 330 associated with a recipient of the incomingupdate 220. The messaging server 110 may comprise a messaging server towhich the recipient is assigned, or may comprise a server currentlyexecuting various processes, such as messaging workers, executingfunctions for the messaging system 100.

The messaging server 110 may comprise a queue management component 550.The queue management component 550 may be operative to determine anincoming recipient sequence number for the recipient update queue 330,the incoming recipient sequence number determined by incrementing ahighest current recipient sequence number for the recipient update queue330, assign the incoming recipient sequence number to the incomingupdate 220, add the incoming update 220 to the recipient update queue330, determine a current recipient sequence number 450 for a currentrecipient update state of a recipient messaging endpoint 410 associatedwith the recipient of the incoming update 220, determine that theincoming recipient sequence number is greater than the current recipientsequence number 450 for the current recipient update state of therecipient messaging endpoint 410, and update the current recipientsequence number 450 for the current recipient update state of therecipient messaging endpoint 410 to be at least the incoming recipientsequence number.

The messaging server 110 may comprise an outbound messaging component560. The outbound messaging component may be operative to transmit theincoming update 220 to the recipient messaging endpoint 410 based on thedetermination that the incoming recipient sequence number is greaterthan the current recipient sequence number 450.

The incoming update 220 may correspond to an atomic modification to amessage inbox for the recipient messaging endpoint 410. The recipientmessaging endpoint 410 may comprise one of a messaging application on adevice, such as a mobile device, and a web browser session. Therecipient messaging endpoint 410 may comprise an archival mail server.The recipient messaging endpoint 410 may comprise a snapshot componentmaintaining a inbox snapshot for quick-setup of messaging inboxes.

The queue management component 550 may determine that a plurality ofupdates in the recipient update queue 330 are each associated with asequence number greater than the current recipient sequence number 450of the recipient messaging endpoint 410. The outbound messagingcomponent 560 may transmit the plurality of updates to the recipientmessaging endpoint 410 based on the determination that the plurality ofupdates in the recipient update queue 330 are each associated with asequence number greater than the current recipient sequence number 450.

A plurality of current recipient sequence numbers may be stored inassociation with the recipient update queue 330. The queue managementcomponent 550 determining the current recipient sequence number 450 forthe current recipient update state of the recipient messaging endpoint410 may comprise the queue management component 550 retrieving thecurrent recipient sequence number 450 based on an identifier for therecipient messaging endpoint 410.

Each of the plurality of current recipient sequence numbers may beassociated with a different recipient messaging endpoint. The queuemanagement component 550 may be operative to determine that everycurrent recipient sequence number of the plurality of current recipientsequence numbers is greater than a sequence number for an old updatestored in the recipient update queue 330 and remove the old update fromthe recipient update queue 330 in response to the determination thatevery current recipient sequence number of the plurality of currentrecipient sequence numbers is greater than the sequence number for theold update.

The queue management component 550 may be operative to receive anotification of an opening of a network connection with the recipientmessaging endpoint 410 and retrieve the current recipient sequencenumber 450 for the current recipient update state of the recipientmessaging endpoint 410 in response to receiving the notification of theopening of the network connection.

The queue management component 550 may be operative to check, inresponse to receiving the incoming update 220 at the recipient updatequeue 330, whether a network connection is already open with therecipient messaging endpoint 410, determine that the network connectionis already open with the recipient messaging endpoint 410, and determinethe current recipient sequence number 450 for the current recipientupdate state of the recipient messaging endpoint 410 in response to thedetermination that the network connection is already open with therecipient messaging endpoint 410. Alternatively, the outbound messagingcomponent 560 may be operative to determine, in response to thedetermination that the incoming recipient sequence number is greaterthan the current recipient sequence number 450 for the current recipientupdate state of the recipient messaging endpoint 410, that a networkconnection is already open with the recipient messaging endpoint 410 andto transmit the incoming update 220 to the recipient messaging endpoint410 based on the determination that the network connection is alreadyopen. Where a plurality of recipient messaging endpoints are associatedwith a recipient update queue 330, the queue management component 550may be operative to check whether network connections are already openwith any of the plurality of recipient messaging endpoints, determinethat one or more network connections are already open with one or moreof the plurality of recipient messaging endpoints, and determine one ormore current recipient sequence numbers for one or more currentrecipient update states of the one or more recipient messaging endpointsin response to the determination that the one or more networkconnections are already open with the one or more recipient messagingendpoints.

It will be appreciated that multiple incoming updates may be stored in asender update queue 230. In many cases, a plurality of incoming updatesmay be addressed to different recipients. As such, different incomingupdates of the plurality of incoming updates may be forward to differentrecipient update queues. When processing a plurality of incomingupdates, the queue management component 550 may determine one or morerecipient update queues, wherein each of the plurality of incomingupdates is associated with one or more of the one or more recipientupdate queues. A single incoming update may be associated with more thanone recipient update queue when that update effects multiple recipients(e.g., is a message addressed to multiple recipients). The queuemanagement component 550 may forward each incoming update to each of therecipient update queues it relates to. As such, updates passing througha single sender update queue 230 may result in multiple recipient updatequeues receiving updates.

The incoming update 220 may be received at the recipient update queue330 from a sender update queue 230 associated with a sender of theincoming update. The sender update queue 230 may be maintained by amessaging server 510. The messaging server 510 may comprise a distinctmessaging server or may be implemented by a same device as the firstmessaging server 110.

The incoming update 220 may received at the recipient update queue 330from a group discussion thread update queue, the group discussion threadupdate queue associated with a group discussion thread. A groupdiscussion thread may comprise any form of ongoing conversation betweentwo or more parties. Multiple messages from the a single participant maybe included within the group discussion thread. In some cases, a userthat joins an ongoing group discussion thread may only be privy tomessages posted to the group discussion thread after their arrival. Insome cases, a user that joins an ongoing group discussion thread mayhave access to the some portion of or the entire history of the groupdiscussion thread prior to their arrival.

A group discussion thread may be associated with a group discussionthread update queue substantially similar to the sender update queue 230and recipient update queue 330. However, the group discussion threadupdate queue may be a temporary queue created to specifically track theprogress of a group discussion thread and distribute updates to thegroup discussion thread to one or more messaging endpoints for one ormore participants. The group discussion thread update queue may bedeleted or otherwise removed from storage and active maintenance atconclusion of the discussion.

An inbound messaging component 540 may receive the incoming update 220at the group discussion thread update queue from a sender messagingqueue 230, determine an incoming group discussion thread sequence numberfor the group discussion thread update queue, the incoming groupdiscussion thread sequence number determined by incrementing a highestcurrent group discussion thread sequence number for the group discussionthread update queue, assign the incoming group discussion threadsequence number to the incoming update 220 at the group discussionthread update queue, add the incoming update 220 to the group discussionthread update queue, and queue one or more workers to forward theincoming update 220 to one or more recipient update queues, wherein eachof the one or more recipient update queues is associated with a followerof the group discussion thread.

In another embodiment, updates may not pass through the message queuesof the group discussion thread participants. Instead, the groupdiscussion thread participants may subscribe to the group discussionthread and directly insert and/or retrieve updates into the groupdiscussion thread update queue. This may make the messaging endpoints ofthe participants the direct subscribers of the group discussion threadqueue rather than the updates for the group discussion thread queuebeing passed through their respective message queues.

Other special-purpose update queues may be created that are notassociated with maintaining a message inbox for a particular user. Forexample, a network-based application may be associated with anapplication update queue. A particular instance of one or more user'sinteraction with an application may be associated with an applicationupdate queue. For example, communication for an online multiplayer gamemay be implemented using an application update queue. Updates on theapplication update queue may correspond to player moves in the onlinemultiplayer game, chat messages in a chat for the game, and other gamestatus updates.

FIG. 6 illustrates an embodiment of a messaging server managing a senderupdate queue.

The incoming update 220 may be received at the recipient update queue330 from a sender update queue 230 associated with a sender of theincoming update 220. The sender update queue 230 may be maintained by amessaging server 510 substantially similar to the messaging server 110maintaining the recipient update queue 330. The messaging server 510 mayalso comprise an inbound messaging component 540, queue managementcomponent 550, and outbound messaging component 560.

The inbound messaging component 540 may be operative to receive theincoming update 220 at the sender update queue 230 from a sendermessaging endpoint 210. The queue management component 550 may beoperative to determine an incoming sender sequence number for the senderupdate queue 230, the incoming sender sequence number determined byincrementing a highest current sender sequence number for the senderupdate queue 230, assign the incoming sender sequence number to theincoming update 220, add the incoming update 220 to the sender updatequeue 230, and queue a worker to forward the incoming update 220 to therecipient update queue 330.

The queue management component 550 may determine a current sendersequence number for a current sender update state of a second sendermessaging endpoint associated with the sender of the incoming update220. The queue management component 550 may determine that the incomingsender sequence number is greater than the current sender sequencenumber for the current sender update state of the second sendermessaging endpoint. The outbound messaging component 560 may transmitthe incoming update 220 to the second sender messaging endpoint based onthe determination that that the incoming sender sequence number isgreater than the current sender sequence number. The queue managementcomponent 550 may update the current sender sequence number for thecurrent sender update state of the second sender messaging endpoint tobe at least the incoming sender sequence number. As such, the secondsender messaging endpoint may be updated with a change made at the firstsender messaging endpoint 210.

Update queues such as the sender update queue 230 and recipient updatequeue 330 may be manipulated in atomic operations performed by workers.Workers may be implemented by worker threads. Workers may lock an updatequeue prior to modifying the update queue, perform their tasks, and thenunlock the update queue after the task is performed. Where multipleworkers have tasks to perform on a particular update queue—for example,there are multiple incoming updates—the multiple workers may be queuedor otherwise put on hold and allowed to act in sequence.

An update may come into a network socket from messaging endpoint and beplaced into an input queue for the update queue. An input processingworker may be kicked, if asleep, to retrieve the update and place itinto the update queue, which may be delayed if the input processingworker has to hold to wait for the update queue to be available due to alock. Placing the update into the update queue may include assigning itthe next sequence number for the update queue.

Once the update is placed into the update queue and assigned a sequencenumber one or more workers may be activated to process the update. Aninbox replication group of one or more inbox replication workers may beactivated to replicate the update to the inbox across all messagingendpoints associated with the update queue. One inbox replication workermay be activated for each messaging endpoint associated with the updatequeue. The inbox replication workers may transmit the update to eachmessaging endpoint as soon as it is available, which may include waitingfor a messaging endpoint that is currently offline to come online.

An archival worker may be activated to transmit the update to archivalstorage for the message inbox associated with the update queue. Archivalstorage may include a message archive server. A message archive servermay be substantially similar to a traditional mail server, and may bereferenced where messages older than those stored in the update queueare to be retrieved. Archival storage may include a snapshot component,the snapshot component building an up-to-date snapshot of a currentstate of a message inbox for quick retrieval by a messaging endpointthat does not maintain state or a new messaging endpoint otherwise beinginitiated.

A distribution group of one or more distribution workers may beactivated to forward the update to any other update queues associatedwith the update. For instance, if the update is the addition of a newmessage, the other update queues may be update queues for the recipientsof the new message. One distribution worker may be activated for eachadditional update queue to receive the update. The distribution workersmay transmit the update to each additional update queue as soon as it isavailable, which may include waiting for a messaging server maintainingan update queue that is currently offline—such as for planned orunplanned downtime—to come online.

Update queues may be replicated across multiple servers. For example, anupdate queue may be replicated in multiple geographic areas to providefaster access to the queue. For example, the messaging system 100 may beprimarily based out of a first geographic area, with all of the updatequeues present in that first geographic area, with a local presence inadditional geographic areas. A user in a second geographic area may havea replication of their update queue be present on a server in thatsecond geographic area. In some cases, one of the replications of theupdate queue may be primary, with all new updates being sent to theupdate queue to be assigned a sequence number and then forwarded to theother replications of the update queue for faster access as variousmessaging endpoints associated with the update queue come online.

Sequential Message Reader

FIG. 7 illustrates an embodiment of messaging endpoints sending andreceiving a message. An incoming update 220 may be produced by a sendermessaging endpoint 210, be processed by a messaging server 510 for thesender, a messaging server 110 for the receiver, and then arrive arecipient messaging endpoint 410. The recipient messaging endpoint 410may comprise a network component 740, inbox management component 750,and display component 760.

The network component 740 may be arranged to receiving an incomingupdate 220 at the recipient messaging endpoint 410 from a recipientupdate queue 330 maintained by a messaging server 110 assigned to therecipient messaging endpoint 410. The incoming update 220 may comprisean incoming recipient sequence number.

The inbox management component 750 may be arranged to add the incomingupdate 220 to a message inbox on the recipient messaging endpoint 410,the incoming update 220 added to the message inbox in an orderdetermined by the incoming recipient sequence number. The inboxmanagement component 750 may determine based on the incoming recipientsequence number whether one or more additional updates are missing fromthe message inbox on the recipient messaging endpoint 410. The incomingupdate 220 may comprise an atomic modification to a message inbox forthe recipient messaging endpoint 410. The incoming update 220 may bereceived in response to a determination that a current recipientsequence number associated with the recipient messaging endpoint 410 inthe recipient update queue 330 is less than the incoming recipientsequence number.

The inbox management component 750 may determine based on the incomingrecipient sequence number that the one or more additional updates aremissing from the message inbox on the messaging endpoint. The inboxmanagement component 750 may determine a smallest missing sequencenumber based on the incoming recipient sequence number. The networkcomponent 740 may transmit a missing update request from the recipientmessaging endpoint 410 to the recipient update queue 330, the missingupdate request comprising the smallest missing sequence number. Thenetwork component 740 may receive the one or more additional updatesfrom the recipient update queue 330 in response to the missing updaterequest.

Where two or more additional updates are missing two or more missingsequence numbers may be determined based on the incoming recipientsequence number, the two or more missing sequence numbers correspondingto the two or more additional updates. A bulk missing update request maybe transmitted from the recipient messaging endpoint 410 to therecipient update queue 330, the bulk missing update request comprisingthe two or more missing sequence numbers. The two or more additionalupdates may be received from the recipient update queue 330 in responseto the missing update request, the two or more additional updatesreceived in a bulk missing update response in a single networktransaction. In some cases, multiple missing updates may cancel eachother out, such as where a message is created and then deleted. Themessaging server 110 may, rather than transmitting updates that couldcancel each other out, replace the updates with no-operation updatesthat produce the same effect.

The recipient messaging endpoint 410 may comprise a user interfacecomponent operative to receive user input for creation of the incomingupdate 220 and create the incoming update 220. The network component 740may transmit the incoming update 220 to the recipient update queue 330.This may correspond to a scenario in which the incoming update 220 isproduced by the recipient messaging endpoint 410 and then transmittedback to the recipient messaging endpoint 410 in confirmation of theincoming update 220 being applied to the recipient update queue 330.Similarly, where the incoming update 220 is produced by the sendermessaging endpoint 210 the messaging server 510 may transmit theincoming update 220 back to the sender messaging endpoint 210.

In some embodiments, the transmission of an update back to the messagingendpoint may be a reduced version of the update excluding informationalready present on the messaging endpoint. For instance, the messagingendpoint may already include the text of a message produced on themessaging endpoint and not be benefited from receiving a duplicate copyof the text. As such, the text may be excluded from the updatetransmitted back to the messaging endpoint.

Adding the incoming update 220 to the message inbox may compriseapplying the incoming update 220 to a message cache 760 of a messagingapplication on a device and applying the incoming update 220 to amessage database of the messaging application on the device. The messagecache may be used by a display component 760 of the messagingapplication to determine the messages to display on the device and mayprovide faster access to the message inbox than provided by the messagedatabase. The message database of the messaging application may be usedto maintain a persistent store of the message inbox for the messagingapplication.

A messaging endpoint, such as a sender messaging endpoint 210 or arecipient messaging endpoint 410, may experience intermittent networkconnectivity. For example, a mobile device may lose contact with acellular station providing cellular data, a mobile device may be put in“airplane mode” and thereby instructed to stop data transmissions, amobile device may deactivate one or more radio devices in order toconserve power, etc. As such, a messaging endpoint may sometimestransition from experiencing a state of no network connectivity to astate of network connectivity for the device on which it is executed.The messaging endpoint may, in response to determining that a networkconnection has become available, initiate an update request with itsassociated update queue.

Hot Snapshots

FIG. 8 illustrates an embodiment of a snapshot device 810 with asnapshot component 850. The snapshot component 850 may comprise anetwork component 840 and a snapshot component 850. The snapshotcomponent may maintain a current state of a message inbox for rapidretrieval by messaging endpoints for the initial setup of new messagingendpoints and the updating of messaging endpoints whose current state isolder than updates that have been removed from an update queue.

The network component 840 may be operative to receiving an incomingupdate 220. The snapshot component 850 may be operative to retrieve asnapshot 860 for a user associated with the incoming update 220, add theincoming update 220 to the snapshot 860, and remove an oldest update ofthe snapshot 860 from the snapshot 860. The incoming update 220 maycomprise an atomic modification to a message inbox for the recipientmessaging endpoint 410. The snapshot 860 may be associated with one of asender of the incoming update 220 and a recipient of the incoming update220. The incoming update 220 may be received from a recipient updatequeue 330 associated with a recipient of the incoming update 220.

The network component 840 may receive a request 880 from a messagingapplication 830 on a recipient device 820 for the snapshot 860 andtransmit the snapshot 860 to the messaging application 830. The networkcomponent 840 may receive a messaging application refresh request from amessaging application 830 on a recipient device 820, the messagingapplication refresh request indicating that the messaging application830 is further out of date than supported by an update queue for themessaging application 830. The network component 840 may transmit thesnapshot 860 to the messaging application 830.

The incoming update 220 may be received from the update queue inresponse to the update queue determining that the incoming update 220 isassociated with an incoming user sequence number higher than a currentuser sequence number associated with the snapshot component 850 at theupdate queue. The incoming update 220 may be received in parallel to atransmission of the incoming update 220 to an archival mail server. Thetransmission of the snapshot 860 from the snapshot component 850 to themessaging application 830 may empower the messaging application 830 tobypass a retrieval of messages from the archival mail server.

The snapshot 860 may be associated with a group discussion thread. Theincoming update 220 may be received from a group discussion threadupdate queue. The network component 840 may receive a group discussionthread join request from a messaging endpoint, the group discussionthread join request indicating that an additional user is joining thegroup discussion thread. This group discussion thread join request mayhave been forwarded via a component managing the group discussionthread. In response to the group discussion thread join request, thenetwork component 840 may transmit the snapshot 860 to the messagingapplication to bring the messaging endpoint up-to-date with the groupdiscussion thread.

The snapshot component 850 may identifying a messaging threadcorresponding to the incoming update 220 and apply the incoming update220 to the messaging thread. The messaging thread may correspond to aconversation carried out by two or more users of the messaging system100. Where the messaging thread is between two users, the messagingthread may correspond to a canonical representation of the messaginghistory for messaging sent between the two users. One of the two usersmay correspond to a sender of the incoming update 220 and the other tothe recipient of the incoming update 220. Applying the incoming update220 may comprise adding a message to the messaging thread, deleting amessage from the messaging thread, modifying a message in the messagingthread, marking one or more messages in the messaging thread as havingbeen read, or any other modification to the messaging thread.

The snapshot component 850 may determine that a number of messagingthreads stored in a messaging snapshot 860 is greater than a threadstorage limit for the messaging snapshot 860. The thread storage limitfor the messaging snapshot 860 may correspond to a default threadstorage limit, such as twenty threads. In response to determining thatthe number of messaging threads is greater than the thread storagelimit, the snapshot component 850 may identify a least-recently-updatedmessaging thread currently stored in the messaging snapshot 860. Thesnapshot component 850 may then remove the least-recently updatedmessaging thread from the messaging snapshot 860. Removing theleast-recently updated messaging thread may comprise removing all of themessages associated with that least-recently updated messaging threadfrom the snapshot 860. The least-recently updated messaging thread maycomprise the messaging thread of a plurality of messaging threads storedin the snapshot 860 with the least-recent application of an update tothat messaging thread.

The thread storage limit for the messaging snapshot 860 for the user maybe set higher than a default thread storage limit based on anidentification of a high rate of messaging activity by the user. Thethread storage limit for the messaging snapshot 860 for the user may beset lower than a default message store limit based on an identificationof a low rate of messaging activity by the user. A high or low rate ofmessaging activity may correspond to a defined number of messages perday, per week, or per other period of time. A high or low rate ofmessaging activity may correspond to a user being in a particular toppercentile (for a high rate) or a particular bottom percentile (for alow rate) of messaging activity per period of time.

In general, threads that are predicted to be more likely to be read maybe cached. The preference for caching threads that have been morerecently written to may comprise a better prediction than threads whichhave been more recently read. A user may be more likely to visit orrevisit a thread with recent activity (the user sending or receivingmessages in that thread) than that has merely been recently read. Merelyreading a thread may not comprise updating the thread and may,therefore, not indicate that a thread should be retained in the cache.In some embodiments, additional criteria may be used in the selection ofwhich messaging thread to remove from the snapshot 860. For example,threads that correspond to users with which the user associated with thesnapshot 860 has a high friend coefficient may be retained even wherethey are the least-recently updated thread. A high friend coefficientfor a user may correspond to the user having a high degree ofinteraction with that user in a messaging or social-networking service.

In some cases, an incoming update 220 may be for a messaging thread notcurrently represented in the snapshot 860. The snapshot component 850may, therefore, have to retrieve the messaging thread from a messagearchive on a message archive server. The snapshot component 850 maydetermine that the messaging thread is not currently stored in themessaging snapshot 860 and retrieve at least a portion of the messagingthread from a message archive in response. The snapshot component 850may only retrieve a predefined number of the most recent messages in themessaging thread. The snapshot component 850 may store the retrievedportion of the messaging thread in the messaging snapshot 860 and applythe incoming update 220 to the messaging thread.

The message archive may be updated using similar techniques to theupdating of the snapshot 860. However, the message archive and thesnapshot 860 may not be in sync with each other based on not havingreceived the same updates. One of the archive and the snapshot 860 maybe more advanced along a message queue than the other. Where the archiveis more advanced than the snapshot 860, one or more updates received bythe snapshot component 850 for this snapshot 860 may be ignored ashaving already been applied to the snapshot 860. Where the snapshot 860is more advanced than the archive, updates may need to be retrieved andapplied to the retrieved portion of the messaging thread in order tobring the messaging thread up to date with the rest of the snapshot 860.

The portion of the messaging thread retrieved from the message archivemay be associated with a current archive sequence number indicating theprogress of the archive in receiving updates related to this messagingthread. The snapshot component 850 may determine that the currentarchive sequence number is less than a current snapshot sequence number,the current snapshot sequence number corresponding to an update progressfor this snapshot 860. The snapshot component may retrieve one or moreadditional updates based on a difference between a current archivesequence number and the current snapshot sequence number and update theretrieved portion by applying the one or more updates to the retrievedportion. These updates may be retrieved from the same queue thatforwarded the incoming update 220 and should still be available in thatqueue as they are, apparently, still queued for the archive (due to thearchive having not yet applied these updates and therefore being behindin sequence number). The snapshot component 840 may store the updatedretrieved portion in the messaging snapshot 860 and apply the incomingupdate 220 to the messaging thread based on the updated retrievedportion.

Alternatively, the snapshot component 850 may determine that the currentarchive sequence number is greater than a current snapshot sequencenumber and store the retrieved portion in the messaging snapshot 860without updating it, as it is, at least, no less advanced than thesnapshot 860. The snapshot component 850 may then receive additionalupdates, such as through the normal reception of updates from amessaging queue. However, one or more of the additional updates may havealready been applied to the snapshot 860 due to the archive being moreadvanced along the queue. As such, the snapshot component 850 may skipone or more of the additional updates based on the skipped one or moreadditional updates being associated with sequence numbers less than orequal to the current archive sequence number.

In some embodiments, a snapshot 860 may be stored as a connected unitwithin a cache. However, in other embodiments, each messaging thread forthe snapshot 860 may be stored as its own unit subject to individualretrieval, modification, and deletion. To retrieve a messaging thread,the snapshot component 850 may retrieve an index for the snapshot 860from a cache, determine a messaging thread to retrieve from the cacheusing the index, and retrieve the messaging thread based on this index(which may store, for example, retrieval identifiers for each messagingthread cached for the snapshot 860). The snapshot component 850 may thenoperate on the retrieved thread as described herein. In addition, whenretrieving the index, the snapshot component 850 may determine whetherother threads referenced in the index are sufficiently old as to beremoved from the cache. The snapshot component 850 may determine thatone or more threads referenced in the index are older than a predefinedthreshold and mark the one or more threads for deletion from the cache.By only examining the threads when the snapshot is retrieved, somethreads may be allowed to linger longer than the threshold age, butprocessing time may be saved by avoiding retrieving a snapshot 860 onlyto evaluate whether one or more threads should be removed.

Intelligent Messaging

FIG. 9 illustrates an embodiment of a messaging server 110 customizingan incoming update 220 for a recipient messaging endpoint 410. Themessaging server 110 may comprise an update customization component 960for customizing the incoming update 220. Customizing the incoming update220 may be performed based on recipient messaging endpoint parametersstored in a endpoint parameter store 970.

The inbound messaging component 540 may receive an incoming update 220at a recipient update queue 330, the recipient update queue 330associated with a recipient of the incoming update 220. The queuemanagement component 550 may add the incoming update to the recipientupdate queue 330 and determine a recipient messaging endpoint 410 toreceive the incoming update 220.

The update customization component 960 may retrieve one or morerecipient messaging endpoint parameters associated with the recipientmessaging endpoint 410 and generate a customized incoming update 920from the incoming update 220 according to the one or more recipientmessaging endpoint parameters. The outbound messaging component 560 maytransmit the customized incoming update 920 to the recipient messagingendpoint 410. Where a plurality of recipient messaging endpoints are toreceive the incoming update 220, a plurality of customized incomingupdates may be generated with each of the customized incoming updatestransmitted to a corresponding recipient messaging endpoint.

The one or more recipient messaging endpoint parameters may indicate alanguage associated with the recipient messaging endpoint 410. Thecustomized incoming update 920 may comprise an insertion of form text inthe language associated with the recipient messaging endpoint 410. Theincoming update 220 may comprise a form text in a first language, theone or more recipient messaging endpoint parameters indicating a secondlanguage associated with the recipient messaging endpoint 410. Thecustomized incoming update 920 may comprise a replacement of the formtext with a translated form text in the second language. Alternatively,the incoming update 220 may comprise a form text identifier, the one ormore recipient messaging endpoint parameters indicating a languageassociated with the recipient messaging endpoint 410. The customizedincoming update 920 may comprise an insertion of form text in thelanguage associated with the recipient messaging endpoint 410 in placeof the form text identifier.

The incoming update may comprise a media element. The one or morerecipient messaging endpoint parameters may indicate a location of therecipient messaging endpoint 410. The customized incoming update 920 maycomprise an insertion of a content distribution network uniform resourcelocator for retrieval of the media element. The update customizationcomponent 960 may select the content distribution network uniformresource locator from a plurality of content distribution networkuniform resource locators based on the location of the recipientmessaging endpoint 410.

The incoming update 220 may comprise a media element. The one or morerecipient messaging endpoint parameters may indicate a media qualitypreference. Media quality preferences may be determined based on devicedisplay resolution, device processing power, device battery power,device bandwidth availability, and other device factors. The customizedincoming update 920 may comprise an insertion of a retrieval uniformresource locator for retrieval of the media element. The updatecustomization component 960 may select the retrieval uniform resourcelocator from a plurality of retrieval uniform resource locators based onthe media quality preference. The type of network may comprise acellular network, wherein the retrieval uniform resource locatorcorresponding to a reduced-bandwidth version of the media element basedon the type of network being a cellular network. The the media qualitypreference may indicate a screen resolution of the recipient messagingendpoint 410, the retrieval uniform resource locator selected based onthe screen resolution of the recipient messaging endpoint 410.

The update customization component 960 may receive a notification of anopening of a network connection with the recipient messaging endpoint410. The update customization component 960 may receive a status updatefrom the recipient messaging endpoint 410 across the network connection,the status update including the location of the recipient messagingendpoint 410. The update customization component 960 may update the oneor more recipient messaging endpoint parameters to include the locationof the recipient messaging endpoint. The status update may include atype of network used for the network connection. The updatecustomization component 960 may update the one or more recipientmessaging endpoint parameters to include the type of network used forthe network connection.

The update customization component 960 may customize the incoming update220 to produce the customized incoming update 920 based on whatinformation is useful to a messaging endpoint receiving the customizedincoming update 920. Where the messaging endpoint is a mobile devicesuch as a smartphone or tablet, the customized incoming update 920 mayinclude only that information used by a local application on the mobiledevice when displaying messages. Where the messaging endpoint is anarchival mail server, all information available for the incoming update220 may be included. Where the messaging endpoint is a session with aweb browser, the customized incoming update 920 may include only thatinformation used by a web client. Where none of the information in anupdate would be of use to a messaging endpoint, the update may betransmitted as a no-operation update producing no effect on themessaging endpoint.

The incoming update 220 may be associated with a significant quantity ofinformation upon reception by the messaging server 110. For instance,the messaging system 100 may be associated with a social networkingservice. The incoming update 220 may be associated with socialnetworking information about a user producing the incoming update 220.This social networking information may be used for data mining ordisplay on some messaging endpoints, such as a web browser accessing thesocial networking service. This social networking information may beexcluded when producing a customized incoming update 920 forapplications on mobile devices.

Messaging system 100 may include an authorization server (or othersuitable component(s)) that allows users to opt in to or opt out ofhaving their actions logged by messaging system 100 or shared with othersystems (e.g., third-party systems), for example, by setting appropriateprivacy settings. A privacy setting of a user may determine whatinformation associated with the user may be logged, how informationassociated with the user may be logged, when information associated withthe user may be logged, who may log information associated with theuser, whom information associated with the user may be shared with, andfor what purposes information associated with the user may be logged orshared. Authorization servers or other authorization components may beused to enforce one or more privacy settings of the users of messagingapplications through blocking, data hashing, anonymization, or othersuitable techniques as appropriate.

Included herein is a set of flow charts representative of exemplarymethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, for example, in the form of a flowchart or flow diagram, are shown and described as a series of acts, itis to be understood and appreciated that the methodologies are notlimited by the order of acts, as some acts may, in accordance therewith,occur in a different order and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all acts illustrated in a methodology maybe required for a novel implementation.

Logic Flows

FIG. 10A illustrates one embodiment of a logic flow 1000. The logic flow1000 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 10A, the logic flow 1000 mayreceive an incoming update 220 at a recipient update queue 330, therecipient update queue 330 associated with a recipient of the incomingupdate 220 at block 1002.

The logic flow 1000 may determine an incoming recipient sequence numberfor the recipient update queue 330, the incoming recipient sequencenumber determined by incrementing a highest current recipient sequencenumber for the recipient update queue 330 at block 1004.

The logic flow 1000 may assign the incoming recipient sequence number tothe incoming update 220 at block 1006.

The logic flow 1000 may add the incoming update 220 to the recipientupdate queue at block 1008.

The logic flow 1000 may determine a current recipient sequence numberfor a current recipient update state of a recipient messaging endpoint410 associated with the recipient of the incoming update 220 at block1010.

The logic flow 1000 may determine that the incoming recipient sequencenumber is greater than the current recipient sequence number for thecurrent recipient update state of the recipient messaging endpoint 410at block 1012.

The logic flow 1000 may transmit the incoming update 220 to therecipient messaging endpoint 410 based on the determination that theincoming recipient sequence number is greater than the current recipientsequence number at block 1014.

The logic flow 1000 may update the current recipient sequence number forthe current recipient update state of the recipient messaging endpoint410 to be at least the incoming recipient sequence number at block 1016.

FIG. 10B illustrates one embodiment of a logic flow 1020. The logic flow1020 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 10B, the logic flow 1020 mayreceive an incoming update 220 at a messaging endpoint from a recipientupdate queue 330, the incoming update 220 comprising an incomingrecipient sequence number at block 1022.

The logic flow 1020 may add the incoming update 220 to a message inboxon the messaging endpoint, the incoming update 220 added to the messageinbox in an order determined by the incoming recipient sequence numberat block 1024.

The logic flow 1020 may determine based on the incoming recipientsequence number whether one or more additional updates are missing fromthe message inbox on the messaging endpoint at block 1026.

FIG. 10C illustrates one embodiment of a logic flow 1040. The logic flow1040 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 10C, the logic flow 1040 mayreceive an incoming update 220 at a snapshot component 850 at block1042.

The logic flow 1040 may retrieve a messaging snapshot 860 for a userassociated with the incoming update 220 at block 1044.

The logic flow 1040 may add the incoming update 220 to the messagingsnapshot 860 at block 1046.

The logic flow 1040 may remove an oldest update of the messagingsnapshot 860 from the messaging snapshot 860 at block 1048.

FIG. 10D illustrates one embodiment of a logic flow 1060. The logic flow1060 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 10D, the logic flow 1060 mayreceive an incoming update 220 at a recipient update queue 330, therecipient update queue 330 associated with a recipient of the incomingupdate 220 at block 1062.

The logic flow 1060 may add the incoming update 220 to the recipientupdate queue 330 at block 1064.

The logic flow 1060 may determine a recipient messaging endpoint 410 toreceive the incoming update 220 at block 1066.

The logic flow 1060 may retrieve one or more recipient messagingendpoint parameters associated with the recipient messaging endpoint 410at block 1068.

The logic flow 1060 may generate a customized incoming update 920 fromthe incoming update 220 according to the one or more recipient messagingendpoint parameters at block 1070.

The logic flow 1060 may transmit the customized incoming update 920 tothe recipient messaging endpoint 410 at block 1072.

The embodiments are not limited to these examples.

System Embodiments

FIG. 11 illustrates a block diagram of a centralized system 1100. Thecentralized system 1100 may implement some or all of the structureand/or operations for the messaging system 100 in a single computingentity, such as entirely within a single device 1120.

The device 1120 may comprise any electronic device capable of receiving,processing, and sending information for the messaging system 100.Examples of an electronic device may include without limitation anultra-mobile device, a mobile device, a personal digital assistant(PDA), a mobile computing device, a smart phone, a telephone, a digitaltelephone, a cellular telephone, ebook readers, a handset, a one-waypager, a two-way pager, a messaging device, a computer, a personalcomputer (PC), a desktop computer, a laptop computer, a notebookcomputer, a netbook computer, a handheld computer, a tablet computer, aserver, a server array or server farm, a web server, a network server,an Internet server, a work station, a mini-computer, a main framecomputer, a supercomputer, a network appliance, a web appliance, adistributed computing system, multiprocessor systems, processor-basedsystems, consumer electronics, programmable consumer electronics, gamedevices, television, digital television, set top box, wireless accesspoint, base station, subscriber station, mobile subscriber center, radionetwork controller, router, hub, gateway, bridge, switch, machine, orcombination thereof. The embodiments are not limited in this context.

The device 1120 may execute processing operations or logic for themessaging system 100 using a processing component 1130. The processingcomponent 1130 may comprise various hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude devices, logic devices, components, processors, microprocessors,circuits, processor circuits, circuit elements (e.g., transistors,resistors, capacitors, inductors, and so forth), integrated circuits,application specific integrated circuits (ASIC), programmable logicdevices (PLD), digital signal processors (DSP), field programmable gatearray (FPGA), memory units, logic gates, registers, semiconductordevice, chips, microchips, chip sets, and so forth. Examples of softwareelements may include software components, programs, applications,computer programs, application programs, system programs, softwaredevelopment programs, machine programs, operating system software,middleware, firmware, software modules, routines, subroutines,functions, methods, procedures, software interfaces, application programinterfaces (API), instruction sets, computing code, computer code, codesegments, computer code segments, words, values, symbols, or anycombination thereof. Determining whether an embodiment is implementedusing hardware elements and/or software elements may vary in accordancewith any number of factors, such as desired computational rate, powerlevels, heat tolerances, processing cycle budget, input data rates,output data rates, memory resources, data bus speeds and other design orperformance constraints, as desired for a given implementation.

The device 1120 may execute communications operations or logic for themessaging system 100 using communications component 1140. Thecommunications component 1140 may implement any well-knowncommunications techniques and protocols, such as techniques suitable foruse with packet-switched networks (e.g., public networks such as theInternet, private networks such as an enterprise intranet, and soforth), circuit-switched networks (e.g., the public switched telephonenetwork), or a combination of packet-switched networks andcircuit-switched networks (with suitable gateways and translators). Thecommunications component 1140 may include various types of standardcommunication elements, such as one or more communications interfaces,network interfaces, network interface cards (NIC), radios, wirelesstransmitters/receivers (transceivers), wired and/or wirelesscommunication media, physical connectors, and so forth. By way ofexample, and not limitation, communication media 1112, 1142 includewired communications media and wireless communications media. Examplesof wired communications media may include a wire, cable, metal leads,printed circuit boards (PCB), backplanes, switch fabrics, semiconductormaterial, twisted-pair wire, co-axial cable, fiber optics, a propagatedsignal, and so forth. Examples of wireless communications media mayinclude acoustic, radio-frequency (RF) spectrum, infrared and otherwireless media.

The device 1120 may communicate with other devices 1110, 1150 over acommunications media 1112, 1142, respectively, using communicationssignals 1114, 1144, respectively, via the communications component 1140.The devices 1110, 1150 may be internal or external to the device 1120 asdesired for a given implementation.

For example, device 1110 may execute a messaging endpoint for a user.The device 1110 may comprise a mobile device executing a local messagingapplication in communication with the messaging server 1190 executing onthe device 1120 for sending and receiving messages. The device 1110 maycomprise a device executing a web browser application in communicationwith the messaging server 1190 executing on the device 1110 for sendingand receiving messages. The communication between the device 1110 anddevice 1120 may comprise the signals 1114 transmitted over media 1112.

Device 1150 may execute a messaging endpoint for a second user. Thedevice 1150 may comprise a mobile device executing a local messagingapplication in communication with the messaging server 1190 executing onthe device 1120 for sending and receiving messages. The device 1150 maycomprise a device executing a web browser application in communicationwith the messaging server 1190 executing on the device 1120 for sendingand receiving messages. The communication between the device 1150 anddevice 1120 may comprise the signals 1144 transmitted over media 1142.

FIG. 11 may represent a scenario in which the device 110 is themessaging server 1190 for both the sender and receiver of a message. Themessaging server 1190 will maintain the sender message queue andrecipient message queue for the sender and receiver respectively. Themessaging server 1190 may receive a message from the sender messagingendpoint, placing the message in the sender queue, forward the messagefrom the sender queue to the recipient queue, then send the message fromthe recipient queue to the recipient messaging endpoint.

FIG. 12 illustrates a block diagram of a distributed system 1200. Thedistributed system 1200 may distribute portions of the structure and/oroperations for the messaging system 100 across multiple computingentities. Examples of distributed system 1200 may include withoutlimitation a client-server architecture, a 3-tier architecture, anN-tier architecture, a tightly-coupled or clustered architecture, apeer-to-peer architecture, a master-slave architecture, a shareddatabase architecture, and other types of distributed systems. Theembodiments are not limited in this context.

The distributed system 1200 may comprise a client device 1210 and aserver device 1250. In general, the client device 1210 and the serverdevice 1250 may be the same or similar to the client device 820 asdescribed with reference to FIG. 8. For instance, the client system 1210and the server system 1250 may each comprise a processing component 1230and a communications component 1240 which are the same or similar to theprocessing component 830 and the communications component 840,respectively, as described with reference to FIG. 8. In another example,the devices 1210, 1250 may communicate over a communications media 1212using communications signals 1214 via the communications components1240.

The client device 1210 may comprise or employ one or more clientprograms that operate to perform various methodologies in accordancewith the described embodiments. In one embodiment, for example, theclient device 1210 may implement the messaging server 110.

The server device 1250 may comprise or employ one or more serverprograms that operate to perform various methodologies in accordancewith the described embodiments. In one embodiment, for example, theserver device 1250 may implement the messaging server 510.

Signals 1214 sent over media 1212 may comprise the exchange of messagesbetween the messaging server 110 and the messaging server 510. Forinstance, incoming update 220 may be transmitted from the messagingserver 510 to the messaging server 110. In general, a plurality ofmessages may be transmitted from the messaging server 510 to themessaging server 110 as part of the operation of the messaging system100. In general, a plurality of messages may be transmitted from themessaging server 110 to the messaging server 510 as part of theoperation of the messaging system 100.

FIG. 13 illustrates an embodiment of an exemplary computing architecture1300 suitable for implementing various embodiments as previouslydescribed. In one embodiment, the computing architecture 1300 maycomprise or be implemented as part of an electronic device. Examples ofan electronic device may include those described with reference to FIG.8, among others. The embodiments are not limited in this context.

As used in this application, the terms “system” and “component” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are provided by the exemplary computingarchitecture 1300. For example, a component can be, but is not limitedto being, a process running on a processor, a processor, a hard diskdrive, multiple storage drives (of optical and/or magnetic storagemedium), an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a server and the server can be a component. One or more componentscan reside within a process and/or thread of execution, and a componentcan be localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 1300 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 1300.

As shown in FIG. 13, the computing architecture 1300 comprises aprocessing unit 1304, a system memory 1306 and a system bus 1308. Theprocessing unit 1304 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 1304.

The system bus 1308 provides an interface for system componentsincluding, but not limited to, the system memory 1306 to the processingunit 1304. The system bus 1308 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 1308 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 1300 may comprise or implement variousarticles of manufacture. An article of manufacture may comprise acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Embodiments may also beat least partly implemented as instructions contained in or on anon-transitory computer-readable medium, which may be read and executedby one or more processors to enable performance of the operationsdescribed herein.

The system memory 1306 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedembodiment shown in FIG. 13, the system memory 1306 can includenon-volatile memory 1310 and/or volatile memory 1312. A basicinput/output system (BIOS) can be stored in the non-volatile memory1310.

The computer 1302 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal (or external) hard disk drive (HDD) 1314, a magnetic floppydisk drive (FDD) 1316 to read from or write to a removable magnetic disk1318, and an optical disk drive 1320 to read from or write to aremovable optical disk 1322 (e.g., a CD-ROM or DVD). The HDD 1314, FDD1316 and optical disk drive 1320 can be connected to the system bus 1308by a HDD interface 1324, an FDD interface 1326 and an optical driveinterface 1328, respectively. The HDD interface 1324 for external driveimplementations can include at least one or both of Universal Serial Bus(USB) and IEEE 1394 interface technologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 1310, 1312, including anoperating system 1330, one or more application programs 1332, otherprogram modules 1334, and program data 1336. In one embodiment, the oneor more application programs 1332, other program modules 1334, andprogram data 1336 can include, for example, the various applicationsand/or components of the messaging system 100.

A user can enter commands and information into the computer 1302 throughone or more wire/wireless input devices, for example, a keyboard 1338and a pointing device, such as a mouse 1340. Other input devices mayinclude microphones, infra-red (IR) remote controls, radio-frequency(RF) remote controls, game pads, stylus pens, card readers, dongles,finger print readers, gloves, graphics tablets, joysticks, keyboards,retina readers, touch screens (e.g., capacitive, resistive, etc.),trackballs, trackpads, sensors, styluses, and the like. These and otherinput devices are often connected to the processing unit 1304 through aninput device interface 1342 that is coupled to the system bus 1308, butcan be connected by other interfaces such as a parallel port, IEEE 1394serial port, a game port, a USB port, an IR interface, and so forth.

A monitor 1344 or other type of display device is also connected to thesystem bus 1308 via an interface, such as a video adaptor 1346. Themonitor 1344 may be internal or external to the computer 1302. Inaddition to the monitor 1344, a computer typically includes otherperipheral output devices, such as speakers, printers, and so forth.

The computer 1302 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 1348. The remote computer1348 can be a workstation, a server computer, a router, a personalcomputer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1302, although, for purposes of brevity, only a memory/storage device1350 is illustrated. The logical connections depicted includewire/wireless connectivity to a local area network (LAN) 1352 and/orlarger networks, for example, a wide area network (WAN) 1354. Such LANand WAN networking environments are commonplace in offices andcompanies, and facilitate enterprise-wide computer networks, such asintranets, all of which may connect to a global communications network,for example, the Internet.

When used in a LAN networking environment, the computer 1302 isconnected to the LAN 1352 through a wire and/or wireless communicationnetwork interface or adaptor 1356. The adaptor 1356 can facilitate wireand/or wireless communications to the LAN 1352, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 1356.

When used in a WAN networking environment, the computer 1302 can includea modem 1358, or is connected to a communications server on the WAN1354, or has other means for establishing communications over the WAN1354, such as by way of the Internet. The modem 1358, which can beinternal or external and a wire and/or wireless device, connects to thesystem bus 1308 via the input device interface 1342. In a networkedenvironment, program modules depicted relative to the computer 1302, orportions thereof, can be stored in the remote memory/storage device1350. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1302 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.13 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.13x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

FIG. 14 illustrates a block diagram of an exemplary communicationsarchitecture 1400 suitable for implementing various embodiments aspreviously described. The communications architecture 1400 includesvarious common communications elements, such as a transmitter, receiver,transceiver, radio, network interface, baseband processor, antenna,amplifiers, filters, power supplies, and so forth. The embodiments,however, are not limited to implementation by the communicationsarchitecture 1400.

As shown in FIG. 14, the communications architecture 1400 comprisesincludes one or more clients 1402 and servers 1404. The clients 1402 mayimplement the client device 910. The servers 1404 may implement theserver device 950. The clients 1402 and the servers 1404 are operativelyconnected to one or more respective client data stores 1408 and serverdata stores 1410 that can be employed to store information local to therespective clients 1402 and servers 1404, such as cookies and/orassociated contextual information.

The clients 1402 and the servers 1404 may communicate informationbetween each other using a communication framework 1406. Thecommunications framework 1406 may implement any well-knowncommunications techniques and protocols. The communications framework1406 may be implemented as a packet-switched network (e.g., publicnetworks such as the Internet, private networks such as an enterpriseintranet, and so forth), a circuit-switched network (e.g., the publicswitched telephone network), or a combination of a packet-switchednetwork and a circuit-switched network (with suitable gateways andtranslators).

The communications framework 1406 may implement various networkinterfaces arranged to accept, communicate, and connect to acommunications network. A network interface may be regarded as aspecialized form of an input output interface. Network interfaces mayemploy connection protocols including without limitation direct connect,Ethernet (e.g., thick, thin, twisted pair 10/100/1000 Base T, and thelike), token ring, wireless network interfaces, cellular networkinterfaces, IEEE 802.11a-x network interfaces, IEEE 802.16 networkinterfaces, IEEE 802.20 network interfaces, and the like. Further,multiple network interfaces may be used to engage with variouscommunications network types. For example, multiple network interfacesmay be employed to allow for the communication over broadcast,multicast, and unicast networks. Should processing requirements dictatea greater amount speed and capacity, distributed network controllerarchitectures may similarly be employed to pool, load balance, andotherwise increase the communicative bandwidth required by clients 1402and the servers 1404. A communications network may be any one and thecombination of wired and/or wireless networks including withoutlimitation a direct interconnection, a secured custom connection, aprivate network (e.g., an enterprise intranet), a public network (e.g.,the Internet), a Personal Area Network (PAN), a Local Area Network(LAN), a Metropolitan Area Network (MAN), an Operating Missions as Nodeson the Internet (OMNI), a Wide Area Network (WAN), a wireless network, acellular network, and other communications networks.

FIG. 15 illustrates an embodiment of a device 1500 for use in amulticarrier OFDM system, such as the messaging system 100. Device 1500may implement, for example, software components 660 as described withreference to messaging system 100 and/or a logic circuit 1530. The logiccircuit 1530 may include physical circuits to perform operationsdescribed for the messaging system 100. As shown in FIG. 15, device 1500may include a radio interface 1510, baseband circuitry 1520, andcomputing platform 1530, although embodiments are not limited to thisconfiguration.

The device 1500 may implement some or all of the structure and/oroperations for the messaging system 100 and/or logic circuit 1530 in asingle computing entity, such as entirely within a single device.Alternatively, the device 1500 may distribute portions of the structureand/or operations for the messaging system 100 and/or logic circuit 1530across multiple computing entities using a distributed systemarchitecture, such as a client-server architecture, a 3-tierarchitecture, an N-tier architecture, a tightly-coupled or clusteredarchitecture, a peer-to-peer architecture, a master-slave architecture,a shared database architecture, and other types of distributed systems.The embodiments are not limited in this context.

In one embodiment, radio interface 1510 may include a component orcombination of components adapted for transmitting and/or receivingsingle carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK) and/or orthogonal frequency divisionmultiplexing (OFDM) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 1510 may include, for example, a receiver 1512, a transmitter1516 and/or a frequency synthesizer 1514. Radio interface 1510 mayinclude bias controls, a crystal oscillator and/or one or more antennas1518. In another embodiment, radio interface 1510 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1520 may communicate with radio interface 1510 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 1522 for down converting received signals, adigital-to-analog converter 1524 for up converting signals fortransmission. Further, baseband circuitry 1520 may include a baseband orphysical layer (PHY) processing circuit 1556 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry1520 may include, for example, a processing circuit 1528 for mediumaccess control (MAC)/data link layer processing. Baseband circuitry 1520may include a memory controller 1532 for communicating with processingcircuit 1528 and/or a computing platform 1530, for example, via one ormore interfaces 1534.

In some embodiments, PHY processing circuit 1526 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames, such as radio frames. Alternatively or inaddition, MAC processing circuit 1528 may share processing for certainof these functions or perform these processes independent of PHYprocessing circuit 1526. In some embodiments, MAC and PHY processing maybe integrated into a single circuit.

The computing platform 1530 may provide computing functionality for thedevice 1500. As shown, the computing platform 1530 may include aprocessing component 1540. In addition to, or alternatively of, thebaseband circuitry 1520, the device 1500 may execute processingoperations or logic for the messaging system 100 and logic circuit 1530using the processing component 1540. The processing component 1540(and/or PHY 1526 and/or MAC 1528) may comprise various hardwareelements, software elements, or a combination of both. Examples ofhardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The computing platform 1530 may further include other platformcomponents 1550. Other platform components 1550 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 1500 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, node B,evolved node B (eNB), subscriber station, mobile subscriber center,radio network controller, router, hub, gateway, bridge, switch, machine,or combination thereof. Accordingly, functions and/or specificconfigurations of device 1500 described herein, may be included oromitted in various embodiments of device 1500, as suitably desired. Insome embodiments, device 1500 may be configured to be compatible withprotocols and frequencies associated one or more of the 3GPP LTESpecifications and/or IEEE 1502.16 Standards for WMANs, and/or otherbroadband wireless networks, cited herein, although the embodiments arenot limited in this respect.

Embodiments of device 1500 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1518) for transmission and/orreception using adaptive antenna techniques for beamforming or spatialdivision multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 1500 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1500 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1500 shown in theblock diagram of FIG. 15 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

A computer-implemented method may comprise receiving an incoming updateat a recipient update queue, the recipient update queue associated witha recipient of the incoming update; determining an incoming recipientsequence number for the recipient update queue, the incoming recipientsequence number determined by incrementing a highest current recipientsequence number for the recipient update queue; assigning the incomingrecipient sequence number to the incoming update; adding the incomingupdate to the recipient update queue; determining a current recipientsequence number for a current recipient update state of a recipientmessaging endpoint associated with the recipient of the incoming update;determining that the incoming recipient sequence number is greater thanthe current recipient sequence number for the current recipient updatestate of the recipient messaging endpoint; transmitting the incomingupdate to the recipient messaging endpoint based on the determinationthat the incoming recipient sequence number is greater than the currentrecipient sequence number; and updating the current recipient sequencenumber for the current recipient update state of the recipient messagingendpoint to be at least the incoming recipient sequence number.

A computer-implemented method may further comprise wherein the incomingupdate corresponds to an atomic modification to a message inbox for therecipient messaging endpoint.

A computer-implemented method may further comprise wherein the incomingupdate corresponds to an atomic modification to a message inbox for therecipient messaging endpoint.

A computer-implemented method may further comprise wherein a pluralityof current recipient sequence numbers are stored in association with therecipient update queue, wherein determining the current recipientsequence number for the current recipient update state of the recipientmessaging endpoint comprises retrieving the current recipient sequencenumber based on an identifier for the recipient messaging endpoint,further comprising: receiving an update request from the recipientmessaging endpoint, the update request comprising the identifier for therecipient messaging endpoint.

A computer-implemented method may further comprise wherein a pluralityof current recipient sequence numbers are stored in association with therecipient update queue, each of the plurality of current recipientsequence numbers associated with a different recipient messagingendpoint, further comprising: determining that every current recipientsequence number of the plurality of current recipient sequence numbersis greater than a sequence number for an old update stored in therecipient update queue; and removing the old update from the recipientupdate queue in response to the determination that every currentrecipient sequence number of the plurality of current recipient sequencenumbers is greater than the sequence number for the old update.

A computer-implemented method may further comprise receiving anotification of an opening of a network connection with the recipientmessaging endpoint; and retrieving the current recipient sequence numberfor the current recipient update state of the recipient messagingendpoint in response to receiving the notification of the opening of thenetwork connection.

A computer-implemented method may further comprise checking, in responseto receiving the incoming update at the recipient update queue, whethera network connection is already open with the recipient messagingendpoint; determining that the network connection is already open withthe recipient messaging endpoint; and determining the current recipientsequence number for the current recipient update state of the recipientmessaging endpoint in response to the determination that the networkconnection is already open with the recipient messaging endpoint.

A computer-implemented method may further comprise the incoming updatereceived at the recipient update queue from a sender update queueassociated with a sender of the incoming update, comprising: receivingthe incoming update at the sender update queue from a sender messagingendpoint; determining an incoming sender sequence number for the senderupdate queue, the incoming sender sequence number determined byincrementing a highest current sender sequence number for the senderupdate queue; assigning the incoming sender sequence number to theincoming update at the sender update queue; adding the incoming updateto the sender update queue; and queuing a worker to forward the incomingupdate to the recipient update queue.

A computer-implemented method may further comprise determining a currentsender sequence number for a current sender update state of a secondsender messaging endpoint associated with the sender of the incomingupdate; determining that the incoming sender sequence number is greaterthan the current sender sequence number for the current sender updatestate of the second sender messaging endpoint; transmitting the incomingupdate to the second sender messaging endpoint based on thedetermination that that the incoming sender sequence number is greaterthan the current sender sequence number; and updating the current sendersequence number for the current sender update state of the second sendermessaging endpoint to be at least the incoming sender sequence number.

A computer-implemented method may further comprise the incoming updatereceived at the recipient update queue from a group discussion threadupdate queue, the group discussion thread update queue associated with agroup discussion thread, comprising: receiving the incoming update atthe group discussion thread update queue from a sender messaging queue;determining an incoming group discussion thread sequence number for thegroup discussion thread update queue, the incoming group discussionthread sequence number determined by incrementing a highest currentgroup discussion thread sequence number for the group discussion threadupdate queue; assigning the incoming group discussion thread sequencenumber to the incoming update at the group discussion thread updatequeue; adding the incoming update to the group discussion thread updatequeue; and queuing one or more workers to forward the incoming update toone or more recipient update queues, wherein each of the one or morerecipient update queues is associated with a follower of the groupdiscussion thread.

An apparatus may comprise a processor circuit on a device; a recipientinbound messaging component operative on the processor circuit toreceive an incoming update at a recipient update queue, the recipientupdate queue associated with a recipient of the incoming update; arecipient queue management component operative on the processor circuitto determine an incoming recipient sequence number for the recipientupdate queue, the incoming recipient sequence number determined byincrementing a highest current recipient sequence number for therecipient update queue, assign the incoming recipient sequence number tothe incoming update, add the incoming update to the recipient updatequeue, determine a current recipient sequence number for a currentrecipient update state of a recipient messaging endpoint associated withthe recipient of the incoming update, determine that the incomingrecipient sequence number is greater than the current recipient sequencenumber for the current recipient update state of the recipient messagingendpoint, and update the current recipient sequence number for thecurrent recipient update state of the recipient messaging endpoint to beat least the incoming recipient sequence number; and a recipientoutbound messaging component operative on the processor circuit totransmit the incoming update to the recipient messaging endpoint basedon the determination that the incoming recipient sequence number isgreater than the current recipient sequence number. The apparatus may beoperative to implement any of the computer-implemented methods describedherein.

At least one computer-readable storage medium may comprise instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

A computer-implemented method may comprise receiving an incoming updateat a messaging endpoint from a recipient update queue, the incomingupdate comprising an incoming recipient sequence number; adding theincoming update to a message inbox on the messaging endpoint, theincoming update added to the message inbox in an order determined by theincoming recipient sequence number; and determining based on theincoming recipient sequence number whether one or more additionalupdates are missing from the message inbox on the messaging endpoint.

A computer-implemented method may further comprise the incoming updatecomprising an atomic modification to a message inbox for the messagingendpoint.

A computer-implemented method may further comprise wherein the messagingendpoint comprises one of a messaging application on a device and a webbrowser session.

A computer-implemented method may further comprise wherein the incomingupdate is received in response to a determination that a currentrecipient sequence number associated with the messaging endpoint in therecipient update queue is less than the incoming recipient sequencenumber.

A computer-implemented method may further comprise determining based onthe incoming recipient sequence number that the one or more additionalupdates are missing from the message inbox on the messaging endpoint;determining a smallest missing sequence number based on the incomingrecipient sequence number; transmitting a missing update request fromthe messaging endpoint to the recipient update queue, the missing updaterequest comprising the smallest missing sequence number; and receivingthe one or more additional updates from the recipient update queue inresponse to the missing update request.

A computer-implemented method may further comprise determining based onthe incoming recipient sequence number that the two or more additionalupdates are missing from the message inbox on the messaging endpoint;determining two or more missing sequence numbers based on the incomingrecipient sequence number, the two or more missing sequence numberscorresponding to the two or more additional updates; transmitting a bulkmissing update request from the messaging endpoint to the recipientupdate queue, the bulk missing update request comprising the two or moremissing sequence numbers; and receiving the two or more additionalupdates from the recipient update queue in response to the missingupdate request, the two or more additional updates received in a bulkmissing update response in a single network transaction.

A computer-implemented method may further comprise receiving user inputfor creation of the incoming update; creating the incoming update; andtransmitting the incoming update to the recipient update queue.

A computer-implemented method may further comprise wherein adding theincoming update to the message inbox comprises: applying the incomingupdate to a message cache of a messaging application on a device; andadding the incoming update to a message database of the messagingapplication on the device.

An apparatus may comprise a processor circuit on a device; a networkcomponent operative on the processor circuit to receiving an incomingupdate at a messaging endpoint from a recipient update queue, theincoming update comprising an incoming recipient sequence number; and aninbox management component operative on the processor circuit to add theincoming update to a message inbox on the messaging endpoint, theincoming update added to the message inbox in an order determined by theincoming recipient sequence number and determine based on the incomingrecipient sequence number whether one or more additional updates aremissing from the message inbox on the messaging endpoint. The apparatusmay be operative to implement any of the computer-implemented methodsdescribed herein.

A computer-implemented method may comprise receiving an incoming updateat a snapshot component; retrieving a messaging snapshot for a userassociated with the incoming update; identifying a messaging threadcorresponding to the incoming update; applying the incoming update tothe messaging thread; determining that a number of messaging threadsstored in the messaging snapshot is greater than a thread storage limitfor the messaging snapshot; identifying a least-recently-updatedmessaging thread currently stored in the messaging snapshot; andremoving the least-recently updated messaging thread from the messagingsnapshot.

A computer-implemented method may further comprise he incoming updatereceived from a user update queue associated with the user, wherein theincoming update is received from the update queue in response to theupdate queue determining that the incoming update is associated with anincoming user sequence number higher than a current user sequence numberassociated with the snapshot component at the update queue.

A computer-implemented method may further comprise receiving a messagingapplication request from a messaging application on a device, themessaging application request indicating at least one of that themessaging application is performing an initial setup and that themessaging application is further out of date than supported by an updatequeue for the messaging application; and transmitting the messagingsnapshot to the messaging application.

A computer-implemented method may further comprise the messagingsnapshot associated with a discussion thread, the incoming updatereceived from a discussion thread update queue, further comprising:receiving a discussion thread join request from a messaging endpoint,the discussion thread join request indicating that an additional user isjoining the discussion thread; and transmitting the messaging snapshotto the messaging application.

A computer-implemented method may further comprise the thread storagelimit for the messaging snapshot for the user set higher than a defaultthread storage limit based on an identification of a high rate ofmessaging activity by the user or the thread storage limit for themessaging snapshot for the user set lower than a default message storelimit based on an identification of a low rate of messaging activity bythe user.

A computer-implemented method may further comprise determining that themessaging thread is not currently stored in the messaging snapshot;retrieving at least a portion of the messaging thread from a messagearchive; storing the retrieved portion of the messaging thread in themessaging snapshot; and applying the incoming update to the messagingthread.

A computer-implemented method may further comprise determining that themessaging thread is not currently stored in the messaging snapshot;retrieving at least a portion of the messaging thread from a messagearchive, the retrieved portion associated with a current archivesequence number; determining that the current archive sequence number isless than a current snapshot sequence number; retrieving one or moreadditional updates based on a difference between a current archivesequence number and the current snapshot sequence number; updating theretrieved portion by applying the one or more updates to the retrievedportion; storing the updated retrieved portion in the messagingsnapshot; and applying the incoming update to the messaging thread basedon the updated retrieved portion.

A computer-implemented method may further comprise determining that themessaging thread is not currently stored in the messaging snapshot;retrieving at least a portion of the messaging thread from a messagearchive, the retrieved portion associated with a current archivesequence number; determining that the current archive sequence number isgreater than a current snapshot sequence number; storing the retrievedportion in the messaging snapshot; receiving additional updates; andskipping one or more of the additional updates based on the skipped oneor more additional updates being associated with sequence numbers lessthan or equal to the current archive sequence number.

An apparatus may comprise a processor circuit on a device; a networkcomponent operative on the processor circuit to receive an incomingupdate; and a snapshot component operative on the processor circuit toretrieve a messaging snapshot for a user associated with the incomingupdate; identify a messaging thread corresponding to the incomingupdate; apply the incoming update to the messaging thread; determiningthat a number of messaging threads stored in the messaging snapshot isgreater than a thread storage limit for the messaging snapshot; identifya least-recently-updated messaging thread currently stored in themessaging snapshot; and remove the least-recently updated messagingthread from the messaging snapshot. The apparatus may be operative toimplement any of the computer-implemented methods described herein.

A computer-implemented method may comprise receiving an incoming updateat a recipient update queue, the recipient update queue associated witha recipient of the incoming update; adding the incoming update to therecipient update queue; determining a recipient messaging endpoint toreceive the incoming update; retrieving one or more recipient messagingendpoint parameters associated with the recipient messaging endpoint;generating a customized incoming update from the incoming updateaccording to the one or more recipient messaging endpoint parameters;and transmitting the customized incoming update to the recipientmessaging endpoint.

A computer-implemented method may further comprise the incoming updatecomprising a form text in a first language, the one or more recipientmessaging endpoint parameters indicating a second language associatedwith the recipient messaging endpoint, wherein the customized incomingupdate comprises a replacement of the form text with a translated formtext in the second language.

A computer-implemented method may further comprise the incoming updatecomprising a form text identifier, the one or more recipient messagingendpoint parameters indicating a language associated with the recipientmessaging endpoint, wherein the customized incoming update comprises aninsertion of form text in the language associated with the recipientmessaging endpoint in place of the form text identifier.

A computer-implemented method may further comprise the incoming updatecomprising a media element, the one or more recipient messaging endpointparameters indicating a location of the recipient messaging endpoint,wherein the customized incoming update comprises an insertion of acontent distribution network uniform resource locator for retrieval ofthe media element, further comprising: selecting the contentdistribution network uniform resource locator from a plurality ofcontent distribution network uniform resource locators based on thelocation of the recipient messaging endpoint.

A computer-implemented method may further comprise receiving anotification of an opening of a network connection with the recipientmessaging endpoint; receiving a status update from the recipientmessaging endpoint across the network connection, the status updateincluding the location of the recipient messaging endpoint; and updatingthe one or more recipient messaging endpoint parameters to include thelocation of the recipient messaging endpoint.

A computer-implemented method may further comprise the incoming updatecomprising a media element, the one or more recipient messaging endpointparameters indicating a media quality preference, wherein the customizedincoming update comprises an insertion of a retrieval uniform resourcelocator for retrieval of the media element, further comprising:selecting the retrieval uniform resource locator from a plurality ofretrieval uniform resource locators based on the media qualitypreference.

A computer-implemented method may further comprise receiving anotification of an opening of a network connection with the recipientmessaging endpoint; receiving a status update from the recipientmessaging endpoint across the network connection, the status updateincluding a type of network used for the network connection; andupdating the one or more recipient messaging endpoint parameters toinclude the type of network used for the network connection.

A computer-implemented method may further comprise the type of networkcomprising a cellular network, wherein the retrieval uniform resourcelocator corresponding to a reduced-bandwidth version of the mediaelement.

A computer-implemented method may further comprise the media qualitypreference indicating a screen resolution of the recipient messagingendpoint, the retrieval uniform resource locator selected based on thescreen resolution of the recipient messaging endpoint.

An apparatus may comprise a processor circuit on a device; a recipientinbound messaging component operative on the processor circuit toreceive an incoming update at a recipient update queue, the recipientupdate queue associated with a recipient of the incoming update; arecipient queue management component operative on the processor circuitto add the incoming update to the recipient update queue and determine arecipient messaging endpoint to receive the incoming update; a recipientupdate customization component operative on the processor circuit toretrieve one or more recipient messaging endpoint parameters associatedwith the recipient messaging endpoint and generate a customized incomingupdate from the incoming update according to the one or more recipientmessaging endpoint parameters; and a recipient outbound messagingcomponent operative on the processor circuit to transmit the customizedincoming update to the recipient messaging endpoint. The apparatus maybe operative to implement any of the computer-implemented methodsdescribed herein.

At least one computer-readable storage medium may comprise instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Further, some embodiments may be described using the expression“coupled” and “connected” along with their derivatives. These terms arenot necessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein which form part of one or more embodiments.Rather, the operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers or similar devices.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose or it may comprise a general purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposemachines may be used with programs written in accordance with theteachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these machines will appear from thedescription given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thusthe following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving an incoming update at a snapshot component; retrieving amessaging snapshot for a user associated with the incoming update;identifying a messaging thread corresponding to the incoming update;applying the incoming update to the messaging thread; determining that anumber of messaging threads stored in the messaging snapshot is greaterthan a thread storage limit for the messaging snapshot; identifying aleast-recently-updated messaging thread currently stored in themessaging snapshot; and removing the least-recently updated messagingthread from the messaging snapshot.
 2. The method of claim 1, theincoming update received from a user update queue associated with theuser, wherein the incoming update is received from the update queue inresponse to the update queue determining that the incoming update isassociated with an incoming user sequence number higher than a currentuser sequence number associated with the snapshot component at theupdate queue.
 3. The method of claim 1, comprising: receiving amessaging application request from a messaging application on a device,the messaging application request indicating at least one of that themessaging application is performing an initial setup and that themessaging application is further out of date than supported by an updatequeue for the messaging application; and transmitting the messagingsnapshot to the messaging application.
 4. The method of claim 1, themessaging snapshot associated with a discussion thread, the incomingupdate received from a discussion thread update queue, furthercomprising: receiving a discussion thread join request from a messagingendpoint, the discussion thread join request indicating that anadditional user is joining the discussion thread; and transmitting themessaging snapshot to the messaging application.
 5. The method of claim1, the thread storage limit for the messaging snapshot for the user sethigher than a default thread storage limit based on an identification ofa high rate of messaging activity by the user or the thread storagelimit for the messaging snapshot for the user set lower than a defaultmessage store limit based on an identification of a low rate ofmessaging activity by the user.
 6. The method of claim 1, furthercomprising: determining that the messaging thread is not currentlystored in the messaging snapshot; retrieving at least a portion of themessaging thread from a message archive; storing the retrieved portionof the messaging thread in the messaging snapshot; and applying theincoming update to the messaging thread.
 7. The method of claim 1,further comprising: determining that the messaging thread is notcurrently stored in the messaging snapshot; retrieving at least aportion of the messaging thread from a message archive, the retrievedportion associated with a current archive sequence number; determiningthat the current archive sequence number is less than a current snapshotsequence number; retrieving one or more additional updates based on adifference between a current archive sequence number and the currentsnapshot sequence number; updating the retrieved portion by applying theone or more updates to the retrieved portion; storing the updatedretrieved portion in the messaging snapshot; and applying the incomingupdate to the messaging thread based on the updated retrieved portion.8. The method of claim 1, further comprising: determining that themessaging thread is not currently stored in the messaging snapshot;retrieving at least a portion of the messaging thread from a messagearchive, the retrieved portion associated with a current archivesequence number; determining that the current archive sequence number isgreater than a current snapshot sequence number; storing the retrievedportion in the messaging snapshot; receiving additional updates; andskipping one or more of the additional updates based on the skipped oneor more additional updates being associated with sequence numbers lessthan or equal to the current archive sequence number.
 9. An apparatus,comprising: a processor circuit on a device; a network componentoperative on the processor circuit to receive an incoming update; and asnapshot component operative on the processor circuit to retrieve amessaging snapshot for a user associated with the incoming update;identify a messaging thread corresponding to the incoming update; applythe incoming update to the messaging thread; determining that a numberof messaging threads stored in the messaging snapshot is greater than athread storage limit for the messaging snapshot; identify aleast-recently-updated messaging thread currently stored in themessaging snapshot; and remove the least-recently updated messagingthread from the messaging snapshot.
 10. The apparatus of claim 9, theincoming update received from a user update queue associated with theuser, wherein the incoming update is received from the update queue inresponse to the update queue determining that the incoming update isassociated with an incoming user sequence number higher than a currentuser sequence number associated with the snapshot component at theupdate queue.
 11. The apparatus of claim 9, the thread storage limit forthe messaging snapshot for the user set higher than a default threadstorage limit based on an identification of a high rate of messagingactivity by the user or the thread storage limit for the messagingsnapshot for the user set lower than a default message store limit basedon an identification of a low rate of messaging activity by the user.12. The apparatus of claim 9, the snapshot component operative todetermine that the messaging thread is not currently stored in themessaging snapshot; retrieve at least a portion of the messaging threadfrom a message archive; store the retrieved portion of the messagingthread in the messaging snapshot; and apply the incoming update to themessaging thread.
 13. The apparatus of claim 9, the snapshot componentoperative to determine that the messaging thread is not currently storedin the messaging snapshot; retrieve at least a portion of the messagingthread from a message archive, the retrieved portion associated with acurrent archive sequence number; determine that the current archivesequence number is less than a current snapshot sequence number;retrieve one or more additional updates based on a difference between acurrent archive sequence number and the current snapshot sequencenumber; update the retrieved portion by applying the one or more updatesto the retrieved portion; store the updated retrieved portion in themessaging snapshot; and apply the incoming update to the messagingthread based on the updated retrieved portion.
 14. The apparatus ofclaim 9, the snapshot component operative to determine that themessaging thread is not currently stored in the messaging snapshot;retrieve at least a portion of the messaging thread from a messagearchive, the retrieved portion associated with a current archivesequence number; determine that the current archive sequence number isgreater than a current snapshot sequence number; store the retrievedportion in the messaging snapshot; receive additional updates; and skipone or more of the additional updates based on the skipped one or moreadditional updates being associated with sequence numbers less than orequal to the current archive sequence number.
 15. At least onecomputer-readable storage medium comprising instructions that, whenexecuted, cause a system to: receive an incoming update at a snapshotcomponent; retrieve a messaging snapshot for a user associated with theincoming update; identify a messaging thread corresponding to theincoming update; apply the incoming update to the messaging thread;determine that a number of messaging threads stored in the messagingsnapshot is greater than a thread storage limit for the messagingsnapshot; identify a least-recently-updated messaging thread currentlystored in the messaging snapshot; and remove the least-recently updatedmessaging thread from the messaging snapshot.
 16. The computer-readablestorage medium of claim 15, the incoming update received from a userupdate queue associated with the user, wherein the incoming update isreceived from the update queue in response to the update queuedetermining that the incoming update is associated with an incoming usersequence number higher than a current user sequence number associatedwith the snapshot component at the update queue.
 17. Thecomputer-readable storage medium of claim 15, the thread storage limitfor the messaging snapshot for the user set higher than a default threadstorage limit based on an identification of a high rate of messagingactivity by the user or the thread storage limit for the messagingsnapshot for the user set lower than a default message store limit basedon an identification of a low rate of messaging activity by the user.18. The computer-readable storage medium of claim 15, comprising furtherinstructions that, when executed, cause a system to: determine that themessaging thread is not currently stored in the messaging snapshot;retrieve at least a portion of the messaging thread from a messagearchive; store the retrieved portion of the messaging thread in themessaging snapshot; and apply the incoming update to the messagingthread.
 19. The computer-readable storage medium of claim 15, comprisingfurther instructions that, when executed, cause a system to: determinethat the messaging thread is not currently stored in the messagingsnapshot; retrieve at least a portion of the messaging thread from amessage archive, the retrieved portion associated with a current archivesequence number; determine that the current archive sequence number isless than a current snapshot sequence number; retrieve one or moreadditional updates based on a difference between a current archivesequence number and the current snapshot sequence number; update theretrieved portion by applying the one or more updates to the retrievedportion; store the updated retrieved portion in the messaging snapshot;and apply the incoming update to the messaging thread based on theupdated retrieved portion.
 20. The computer-readable storage medium ofclaim 15, comprising further instructions that, when executed, cause asystem to: determining that the messaging thread is not currently storedin the messaging snapshot; retrieving at least a portion of themessaging thread from a message archive, the retrieved portionassociated with a current archive sequence number; determining that thecurrent archive sequence number is greater than a current snapshotsequence number; storing the retrieved portion in the messagingsnapshot; receiving additional updates; and skipping one or more of theadditional updates based on the skipped one or more additional updatesbeing associated with sequence numbers less than or equal to the currentarchive sequence number.